Hi

I'm a newbie to xoops. Can I use XOOPS to create multiple websites using one centerlized installation/database?

I run a free web hosting, and I need a CMS to create many websites using one installation and one database, to save disk space, and for easier upgrades and modifications.
I need to know please if XOOPS is the one for me?!

anyone please?

In a word, no. You can run a number of XOOPS installations on a single database, but you'd have to use a different database prefix for each installation. You can't however run more than one XOOPS site on a single installation. But then, I don't know of a CMS you can - other than perhaps EZ Publish which is a VERY different system altogether.

In this thread you can read the following, written by Onokazu:


Re: Multiple sites off single codebase
This should be now a lot easier in 2.0.4.

Let's say that you have uploaded all XOOPS files to /var/html/www, and want all other users to share these files.

First, for each of the virtual domains, create mainfile.php in which following constants are defined:
XOOPS_CACHE_PATH, XOOPS_UPLOAD_PATH, XOOPS_THEME_PATH", XOOPS_COMPILE_PATH, XOOPS_THEME_URL, XOOPS_UPLOAD_URL

For example, mainfile.php of 'hogehoge' user will be something like below:

define("XOOPS_CACHE_PATH", "/home/hogehoge/xoops/cache");
define("XOOPS_UPLOAD_PATH", "/home/hogehoge/public_html/uploads");
define("XOOPS_THEME_PATH", "/home/hogehoge/public_html/themes");
define("XOOPS_COMPILE_PATH", "/home/hogehoge/xoops/templates_c");
define("XOOPS_URL", "http://www.hogehoge.com/xoops");
define("XOOPS_THEME_URL", "http://www.hogehoge.com/themes");
define("XOOPS_UPLOAD_URL", "http://www.hogehoge.com/uploads");
define('XOOPS_DB_PREFIX', 'xoops');
define('XOOPS_DB_USER', 'hogehoge_xoops');
define('XOOPS_DB_PASS', 'hogehoge');
define('XOOPS_DB_NAME', 'hogehoge_xoops');

and the directory structure of the user will be like below:

/home/hogehoge/xoops/mainfile.php
/home/hogehoge/xoops/cache/ (chmod 777)
/home/hogehoge/xoops/templates_c/ (chmod 777)
/home/hogehoge/public_html/uploads/ (chmod 777)
/home/hogehoge/public_html/themes/

Next, create symlink between the user directory and the directory where XOOPS core files are uploaded

ln -s /var/html/www /home/homehome/public_html/xoops

The final step is to modify the /var/html/www/mainfile.php file so that it will read mainfile.php placed under the user directory. If you are running Apache you can use $_SERVER['DOCUMENT_ROOT'] to get the directory of the user.


I would like to hear from you if you succeed!

Success!

The only thing missing with the solution is the database end and the modules. The installer sets up the database and creates the initial tables. Can we run installer with this implementation to do that?

Also, I don't think he is refering to mainfile.php to put in these modifications. Isn't he referring to common.php instead. XOOPS_CACHE_PATH, XOOPS_UPLOAD_PATH, XOOPS_THEME_PATH", XOOPS_COMPILE_PATH, XOOPS_THEME_URL and XOOPS_UPLOAD_URL are all in common.php not mainfile.php. If so, then we should write a wrapper for common.php instead of mainfile.php. I'm real confuse with these instructions.

Quote:
Pardon my ignorance, but in the context of XOOPS, how does one create a symlink between two different directories?

I agree and I think "homehome" is a typo also. I think it should be:

ln -s /var/html/www /home/hogehoge/xoops


These lines are also incorrect...

define("XOOPS_THEME_URL", "http://www.hogehoge.com/themes");
define("XOOPS_UPLOAD_URL", "http://www.hogehoge.com/uploads");

It should be:

define("XOOPS_THEME_URL", "http://www.hogehoge.com/public_html/themes");
define("XOOPS_UPLOAD_URL", "http://www.hogehoge.com/public_html/uploads");

I hope ONO clears this up...