Re: Multisite HACK for 2.2.3 Final
It would be better to define and discuss with a better terminology as follows:
Is the site where define('XOOPS_RESCUE_URL', 'http://mastersite.com') is made AND the multisite is installed
- Is a site which is parked on the master.com
- URI / URL is correctly configured in the multisite module
- Only some or many tables are available independently and are NOT shared.
1) I have installed XOOPS 2.2.3, and the multi site hack is the one for 2.2.3
I had a funny problem that made me furious. I downloaded a 2.2.3 from somewhere else and later did not know the difference which iinstallation was correct. One gave a nightmare problems. The other does a similar behaviour after de-installation of modules!
2) I want site2 to use site1's user tables, so site2 can login using site1's details. Do I need to have the multi site hack installed on site1 or site2, it is currently installed on site2 only.
You have a conflict between the mainfile.php and mastersite, in your case site2! Install it on the first master site, in your case site1 ONLY
Please read the first four steps mentioned in the first message by the programmer Jan Pederson of THIS thread and follow this EXACTLY how it is done.
The multisite will work IF AND ONLY IF
the rescue URL matches with the XOOPS installation where all the configuration details and the site details are available in FULL or TOTAL!
See the following is happening:
>>> XOOPS looks for config, config options, modules
>>> no module found of multisite on site1.
>>> Hence there is only one site and that is one and only site1
>>> Type site2 in the browser URL
>>> It will resolve into site1, because that is a command out of cPanel you configured!
For this, you need to have all user and profiles tables shared, like I did. It will however, not recognise the logged in users of site1, when visiting site2 though. This happens due to cookies and browser behaviour so you cannot do anything about it. All the user details will be shared and there would be no need to register again.
The site module (multisites) installed on the first and the master installation, in your case site1, will tell XOOPS about the differenciating URI patterns and connect to the database extracting or retrieving all the necessary details of shared or non-shared tables that are needed for site2.
This follows the logic that you need one and one module installed on the master website, in your case site1, to be installed and working properly.
However, logically speaking, by installing it on other subsites, it may also generate further subsites! In this case you need to install subsites generating out or the module over a subsite and make all the necessary configuration changes in that subsite-module. Howewer, I strongly recommend NOT to install multisite module on subsites.