Hallo Curtt!

Quote:

Well, there are also Owls in Germany! But I do not seem to be one of them!

This solution would be only to have the basic sub-domain possibility. However, you need to individually configure the sub-domain and then enter the config i.e. what YOU SEE in the browser LOCATION into multisite module.

Hallo Curt!
Quote:
I am really glad to have helped someone as I think this module is very nicely programmed with primitive administration. However it works and nobody helped me out.
Quote:
Does your IP also allow adding more IPs to those sub-domains or domains?
Quote:
Sub-domains are also domains with a difference that they are not maintained by the central registry but in your name server. So they are setup locally in the DNS resource files. They resolve from there the same as fully qualified domain names.

Well, I have made a test of 21 sub-domains where NOT ONE DOMAIN was on my server! I have only tested the great multisite module with sub-domains.

You can also have your Domain on my server and use the multisite module with sub-domains on your server, understand?

It is just that you need to correctly insert the real and correct URI pattern in the module to trigger the mainfile.php action, as I have described above.
Quote:
Did you try it out? I seem to not to understand this point. If it is a real test installation problem you are describing about, then either your URI pattern is wrong or there is a problem in the SiteAlias of your httpd.conf / apache2.conf file that does not match somewhere.
Quote:
What I think is definately correct that what you think is wrong! Simply because I have tested only with sub-domains!!!
Quote:
The best result is to have seperate IP addresses mapped to each domain or sub-domains. Not many Host offers this services. This could be extremely useful if one needs SSL at a later date. Otherwise basically you DO NOT NEED it.

If you plan to run ads then you MUST have seperate IPs otherwise the detection scripts may not count and you shall earn less. Beware...

Hallo!

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!

Quote:

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 havehttp://domain.com then simply fill it there. If you wannahttp://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 SiteNamehttp://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.

Quote:

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:

Path: /usr/home/html/domainname1/xoops
Sitename:http://domainname1.com
SiteAlias:http://www.domainname1.com
URI Pattern:http://domainname1.com
URI Pattern:http://www.domainname1.com
(All small letters,http://Domainname1.com SHALL NOT work!)

Path: /usr/home/html/domainname1/xoops
Sitename:http://domainname2.com
SiteAlias:http://www.domainname2.com
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: andhttp://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.

Quote:

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:// ANDhttp://www. pointing to the same subdomain, it does not make much sense to go forward as the module is not properly configured at all.

Hi!

After having a lot of problems, I can now say something about it.

You CANNOT have your URI Pattern BLANK!

You MUST have all the alphabets in your domain name small.

You may not do jump the process of troubleshooting completely.

I advise, before you begin to aliasing your directories, simply get your multisite module working with two domains. Thereafter aliasing could be a step forward, however Mitrandir could better say about the problem.

I aam also not aware of having multisite module working on two directories as it captures REMOTE_HOST, which should be qualified domains of sub-domains. Directories are not qualified for domain resolve.

I would in the begining not clone all the tables. Simply leave all th tables to be shared, except sesssions and module config, config i.e. the basic duplication.

ONCE YOU HAVE A BASIC INSTALLTION CLONING TECHNOLOGY WORKING, you could only then be sure to have eliminated all the fundamental problems of the multisite installation. Thereafter duplication or sharing of tables is a childs game.

Hope this helps.

Hi!

I have updated 2.31 > 3.01 on two production websites after vigiorous checking into each corner! Works flawless!!!

Therefore important is to compare differences through debug...

My serious doubt is bugs in 2.2.3 that gave me various similar problems with WordPress, zenTrackXoops for which I have placed series of messages.

I saw myself to be fooled by discovering that I was erroneously using 2.2.3. It was only after updating to 2.2.4 things worked stable.

However, there is no counter argument not to update.

I did have a similar problem with an anathor module. It was updating 2.2.3 to 2.2.4 helped.

Hi!

I also had a blank page during installation 2.31 >> 3.01. Funny.

It was phppp who have programmed it and I have full trust in him and his programming.

Therefore, I tried for the second time, it worked after a long waiting time.

Do you also like and trust his work?

Maybe you need to step by step update your very old version...

Moreover, I had such a nasty experience installing zenTrackXoops with 2.2.3! See my messages in the forum and News.

Do update to 2.2.4!

Hallo dkeir!

I installed the final version 2.60 on my server on a different installation I fished from the official german website.

The installation went flawless.

Thereafter, I installed on anathor production website and it did not work. There were many more modules, not in use. Well I de-installed one after the other. No chance to get your module working. The same Error.

The fact showed that I could install the latest version on a different installation than the one in question. Same MySQL version and the same error.

Well, I upgraded all the modules including the system ones. No chance.

The only this was in difference was the scripts, which I beleive I downloaded from the older version 2.2.3 from DU version and upgraded to 2.2.4.

The other functioning version was a SIE version.

I copied all the scripts with overwrite.

IT WORKED!

Hence it was the XOOPS scripts in the installation in question where the problem was and not anywhere else. Very surprising. It was I think 2.2.3 or 2.2.3a, or something... Stupid Nightmare as I like this module...

Quote:

Very true. Even though everything was fine everywhere, visibilly to the Admin, it was clearly pointing to a wrong domain.

Quote:

No need. there is a mainfile-dist.php also supplied togather. Editing this would also do the same thing.

Quote:

Thanks Herko! That was the real good tip! It could have been an intelligent Nightmare!

The wrong URL was being generated from the cached version lying in the folder "cache".

I found this out by changing the DIE notice echo to some other text and it was still showing the old notice! Stupid XOOPS cache but very very useful.

Summary:

Duplicating the XOOPS installation and database is very easy. You need to remove everything from the cache and templates_c, especially if you used or turned the cache ON!

Hallo!

I have seen earlier Topics on this subject but did not find any solution. Maybe I am making a mistake.

I have configured everything and its a live XOOPS site on www.Domain1.com.

Now I want to have www.Domain2.com with the SAME installation and database.

With the respective owner and permissions, I duplicated the database, all three files MYI..., and the entire installation of working XOOPS production site.

Therefore, I have a complete duplicate with rrespective owner names and permissions.
----------------

Thereafter I changed the mainfile.php to reflect the correct UNIX path of the duplicate installation and domain + MySQL password and user.

I GET the above error:

XOOPS path check: Script is not inside XOOPS_ROOT_PATH

De-activating the

define('XOOPS_CHECK_PATH', '0');

does not help. The security is still making me nuts.

Anyone had similar problems? Any ideas.

The purpose is to have a parallel Domain as a LIVE backup, with MySQL database copying in the background from LIVE to duplicate domain.

To Forum moderators:

Sorry to bother, but I made a mistake in clickting the grafic of new pst, without realising that the thread belonged to a different forum.

Hence the thread needs to be moved. This may also help others if in an appropriate forum. Really sorry about that.