1
Im refering to an post from Mithrandir in a thread about the multisite hack for 2.2.3.
Quote:
Mithrandir wrote:
Quote:So, a single code core install of XOOPS supporting multiple sites with their own, dedicated, databases. Single point to patch. Possible?
Much easier than hacks and stuff.
On a Apache/Linux server, you can use symlinks so you would have
/websites/common
with all the files and directories except mainfile.php, templates_c, cache and (perhaps) uploads
and for the subsites, you'd have
/websites/site1
/websites/site2
/websites/site2
that would only have mainfile.php, templates_c, cache and (perhaps) uploads and everything else would symlink to the /websites/common files and directories with the sites themselves being virtual hosts on the webserver.
That way, you would only have one core to maintain, but could use individual databases (and database servers) for the sites. No sharing of database tables would be involved, though.
Im currently running around 30 Websites on a Server, each indiviually installed with a complete set of files aswell as an dedicated database.
I would like to reduce maintenance efforts in the future by only updating one "core" folder. Every webpage should have their own database aswell as the "smallest possible" set of files. I already tried it like Mithrandir suggested but im struggling with the XOOPS Security.
I have an full installation at an folder called "xoops_core" and an test web at an folder named "xoops1".
Everything in "xoops1" is symlinked and pointing to "xoops_core" beside:
mainfile.php
.htaccess
(DIR) cache
(DIR) templates_c
(DIR) uploads
After editing the mainfile.php to the proper paths i get the following error message:
Quote:
XOOPS path check: Script is not inside XOOPS_ROOT_PATH and cannot run.
Already tried to change "XOOPS_CHECK_PATH" to 0 without any change.
I appreciate any help. Thanks in advance.
