Yes - please send me the URL and I'll have a look. I may need access to the files, but we'll start here.

What the error message is telling you is that there is a missing definition (ImpressCMS uses constants that can be defined in files - allows for easy translation into other languages). The definition is indeed missing from the language files. I'll report it and have it taken care of. It shouldn't keep your install from progressing, though. It is only a notice - a 'fatal error' in PHP would stop you.

Do you see anything else on that page? Can you continue?

Hello, BroKen1 - are you using IIS as your web server? It seems as though the file and folder permissions are a bit trickier to get right on that. It's not my area of expertise, but we should be able to find some help for you.

Thanks for the tip.

Actually, it's not an issue with the core, it is with the module(s) that filter HTML on output, too - CBB is one of them. It was discussed in the ImpressCMS forums - http://community.impressc ... mp;forum=1

BTW - any makeTareaData4... or makeTboxData... method is outdated. Replace with the proper method as indicated in class/module.textsanitizer.php

Thanks for the notice - the feed is working again. There was an invalid character in one of the articles causing the problem. I should learn not to copy/paste text from other sources.

(I also need to work on the HTML in the forum signatures)

It may, or may not, be relevant in your situation, but here is an article I wrote on this topic, too - An Effective Solution for Church Web Sites.

I've also just found this - Determine Your Goal - the first in a series about church web planning and development. There's lots of good stuff out there and I plan on bringing as much of it together as possible.

Peace!

First off - Welcome, Bassman! I have a thread at XOOPS bookmarked with your admission of having a XOOPS-based church web site. That thread has been very influential in the making of this site. Thank you!

Now, to your question. My answer - "That depends."

Honestly, not all churches are ready to enter the Internet mission field. There's an article by Tim Bednar at Godbit about chosing a web site for your church and it gives us something to think about. How are we serving our churches?If a church needs a 'static' web site, a CMS can serve that purpose. Just install the core and a basic content module, like News, SmartSection or Wiwimod. When they are ready for more, add another rmodule. Eventually, they'll be ready for a fully interactive site. If you just give them a static site at first, how will you add interactivity?

Another interesting bit of research was done to identify what makes a ministry site successful? While I might challenge some of their conclusions, the 3 factors involved - technology, people and processes - are an excellent summary of what we must consider. In my experience, processes play the biggest part in the success of anything. Not to the point of some organizations that elevate processes above effectiveness and results, but if the processes have not been established, then the people can't follow them, using the technology available.

Hi, Steve - welcome to the forums! Another voice is always appreciated.

I have not run across anyone using DMS to manage their documents. I think HelpXOOPS did while it was around. Personally, I would favor a wiki instead. If I recall correctly, with DMS only 1 person can have a document checked out for revision and the others must wait their turn. With a wiki, the document is always available and the revisions are tracked. It depends on your situation and requirements, I guess.