I think you'll find what you're looking for in this thread

I found another 'feature' - the Scripturizer does not work in the Spotlight article in News 1.43, but it does when you view the article. Go figure.

I've seen reference to Scripturizer on HYCW before, but never investigated it further - thanks for the pointer. I donwloaded and tested it on my local server, and it works great! I was worried about links I manually created - Scripturizer replaces those with its own.

I added the js file inside the include folder, then added the reference to the script in my theme.html



I'll be adding this to our site soon. I'm not sure if I use the popup, though. But, I won't have to edit everyone's submissions, and they won't have to do anything extra, either.

Thanks!

[edit] - found a few quirks: the pattern match turned The 22nd into a link (Thessalonians); it doesn't check the volume (the above should have had 1 or 2 in front to be valid). So, someone still needs to proofread the text (a good practice, anyway)[/edit]

Xoops I'm using - 2.0.13, XOOPS you're using - 2.2.3. Therein lies the difference

You'll find the license list in Administration Menu > WF-Downloads > Preferences

We spent a great deal of time discussing how we would provide the ability to submit prayer requests on our site, and we selected Formulize (v1.6 + email hack).

Each church will have different criteria, and here are ours:
1. Availability - it should be available to everyone, just as it is in our services
2. Anonymity - some people would like to remain anonymous, and we respect that
3. Privacy - not all details need to be disclosed (specifics about a surgical procedure, for example), and not all subjects of the prayers know the request is being made on their behalf. Submitters are also able to select the type of prayer for their request - private (ministerial staff, only), prayer chain (limited number of trained lay people), and public (offered during a church service)
4. Discretion - while most visitors and submitters will be discrete, there are those on the web that spam every form and deface web sites. Others miss the point of the request and only seek attention. Since we allow anonymous submission, we must filter the requests.

Formulize allows us to create a form to meet all these criteria, and publish reports to the proper groups of people, based on the type of request. We currently do not publish any requests publicly online. With the email hack, staff can be alerted of a new submission.

A forum would be an excellent way of achieving a public prayer list, allowing moderation of the posts and submissions before they are made public. (Our forum was defaced because of permissions that weren't strict enough).

My desired add-ons for a church site - XOOPS Code, or similar way of tagging Scripture references (I manually add links to online Bibles, now), almost like wiki links. A course module (I still have to look more at OBS Classroom) for study groups.

Steve K
Web Steward @ www.easter.org

@script_fu: Thanks for the feedback. I give a lot of credit to the developers of PGV and the first coder to port it to XOOPS to get me started.

Just a bit of a note on themes within PGVXoops - IE renders the charts a bit funky and I had to add some different stylesheet definitions. Check out the msie.css files in each of the themes I included.

You can set up custom error pages with your host, but how about an error-handler within Xoops? When I was checking out PostNuke, it had such a feature.

I agree with DonXoops approach - rather than develop an image manager independent of a gallery module, I think being able to point the image manager at the gallery module for its images make a lot of sense. There are photos in my gallery I would like to use in my articles, etc., that, under the current implementation, need to be added to the image manager, or add the URLs directly, which makes editors lacking in image insertion.

Most likely a breach of your web server. Check out this article.