Re: Multisite HACK for 2.2.3 Final
Not a very difficult thing to understand after you have done it once. Before things are a nightmare.
URI pattern is a list of http commands for the mainfile.php passed on through the browser location which will make an ARRAY of subsites and differenciate each site. Those Array parameters like domain1.com and www.domain1.com
are passed into an array that interacts with the site specific configuration for that pattern.
Hence you DO NOT have a multisite configured even if you have installed the module correctly, if your URI pattern is not correctly pointing to the correct location capture from the browser. The module will not understand the different sites at all!
Deepy, Thank you for your reply.
Could you give me some examples of Uri Pattern syntax that you used. Is that field looking for a regular expression? And what is the 0 checkbox for? What sort of a uri pattern should I be using to accomplish this?
URI pattern means actually what you want the Module to resolve through the mainfile.php which captures from the browser location.
So if you wanna have http://domain.com
then simply fill it there. If you wanna http://www.subdomain.domain.com
to be seen in the location of the browser an to be passed on to your mainfile.php then enter this in there.
Mind you, this should be also compatible to your apache.conf or httpd.conf in cases of Site-Aliases. For instance in your httpd.conf if you DONOT have SiteName http://www.domain.com
then the URI Pattern of the same SHALL NOT work. You then NEED to have SITEALIAS of the same in your httpd.conf.
Hence the URI pattern is kind if an extension of SiteAliases that are in the http.conf OR the way how a domain resolves in different pattern. Thats the pattern you need to write in there.
This is also a bit troublesoume to configure in there. You need t play a bit. Until you go though the basics of configuration, I advise to refrain from all other additions and complications UNTIL you have mastered the configuration places. Otherwise you will be fighting on different level whereas the problem lies in your URI pattern.
I agree - getting the multisite working in a simple fashion would be the best starting point. So now I have parked a second domainname to the installation of XOOPS on the first domain.
e.g. domainname2.com --> domainname1.com/xoops/
In principle all your Sites should POINT to the same location of a file where the mainfile.php and the installation of XOOPS is there. For instance:
URI Pattern: http://domainname1.com
URI Pattern: http://www.domainname1.com
(All small letters, http://Domainname1.com
SHALL NOT work!)
URI Pattern: http://domainname2.com
URI Pattern: http://www.domainname2.com
In the above example, you see that both the domains point to the same XOOPS directory where the mainfile.php is located. Then you see that the first domain has two domain pattern: http: and http://www.!
So fill the www pattern in the URIO pattern and the mainfile.php will pass this into a site array. By this the mainfile.php will begin to differenciate the two domains having different patterns into THE SAME subsite domain.
You must have atleast ONE domain pattern for the mainfile.php arry to return a positive value. Otherwise it will default or resolve to the default mainsite. The URI pattern entries works like a plattform or a bridge between the browser and the multisite module. It helps to bridge the two and eastabilish a link by generating an Array correctly recognising the subdomain pattern of a particular domain installed through the multisite module.
It would be great if other users submitted examples of how they have used the multisite module - the module is powerful but perhaps a lot of users like myself dont know how to fully tap it???
There are not many users who "cracked" it. Just ask me if you still have problems to understand above!
Mind you, the multisite module works very good with 2.2.3. But there is no 2.2.4 version existing. I have had terrible experiences with 2.2.3 XOOPS and consider ti be buggy. I do NOT recommend. Hoever, it should not be difficult to see the codes of multisites and port it them to 2.2.4. That may be one step after when you may have installed it.
Also, be very very careful with the install and de-install of modules. This entire area is very very raw, even though it may look very proffessional and the core developers may still remain under illusion of it being perfect. However we may discuss them at a later date when you are a step forward.
Unless your mainfile.php begins to resolve into different domains and shows correct URIL pattern, i.e. http:// AND http://www
. pointing to the same subdomain, it does not make much sense to go forward as the module is not properly configured at all.