6
Deepy, thanks for the indepth response. It answered my initial questions quite well. But, unfortunately, has led to others :).
Quote:
If you wanna have an excellent application control, permission and groups features, simply close your eyes and work with XOOPS with some frustration during the installation phase as a beginner. If you are experienced programmer, things will go forward with a simple click in seconds...
Ive tackled some pretty ugly CMS applications before. xoops, in its basic form, installed without a hitch.
Quote:
4. Install multisites module and generate the first subsite1. It is here you decide which tables you wanna clone, including users table, sessions, news, forum, etc. Hence if you have feed all necessary information in the core preferences and also in the modules <SNIP>
This is where I kind of run off the tracks. Maybe a brief list of my requirements will get me straightened out, and help others to understand as well.
First, I must have separate databases for security/privacy reasons. Each day, client databases are dumped, pgp'd and put on an ftp site for client retrieval. As you can imagine, sharing a database would mean all clients would have each others usernames and passwords. Legally, I think this would get me into a mess.
Second, as it currently stands, I have a CMS (which shall remain unamed :) ) codebase installed for EACH client, even though they are all using the same CMS. This leads me to patching each install whenever a security fix is released. This is what I am trying to get away from. I want to patch once, and have it apply to all sites hosted with that particular CMS (hopefully xoops).
Third, I'm a lazy admin. If I didn't admit it, someone would have called me lazy anyway.
So, a single code core install of XOOPS supporting multiple sites with their own, dedicated, databases. Single point to patch. Possible?
Thanks so much for the complete repsonses!
LS.net