Test system
|
zjohn13
Joined: 2010-12-01
Posts: 94 |
Posted: Thu, 2013-12-12 17:28
|
|
I am running Gallery3 in the root of my website www.mydomain/index.php and as this is the only website that I can access I'm running a test Gallery3 installation in www.mydomain/g3test/index.php on the same site. Thanks, |
|
Posts: 814
I've done the same and it presented no issues that I ever encountered.
Posts: 94
Thanks jnash, that gives me the warm feeling of having one less thing to worry about....
John
Posts: 1857
I didn't realize that you can run a second instance of Gallery in a subfolder of another instance of Gallery (at least without modifying the htaccess, etc). I guess it works because the second instance has its own htaccess that's overriding the htaccess of the root folder?
I've always used subdomains as test sites.
Anyway, to your question, I think the biggest issue is to just make sure that you're using different databases. You could use the same db with a prefix, but separate is usually the best idea there.
Posts: 814
That's correct. I assumed that they were isolated appropriately. .htaccess and db inclusive
With this being said, If you have the opportunity to separate them now, that would prevent any 'oddities' experienced. I can probably think of a few module coding errors that -might- pose a problem, but I have yet to experience any myself.
Posts: 94
Two test systems are running on the same server as the production Gallery which is in the website root, all with their own databases and .htaccess files.
I don't have another server to separate them.
There are two different problems that nobody else is experiencing.
The problems are experienced on the three installations, all at 3.0.8, one of the test installations being an out of the box non customised gallery.
My thoughts are running along the lines that I have problems on the root system, most probably introduced during customisation.
Are the root system problems being propagated through to the test systems by the root index.php?
The problems exist when running test systems via subdomains as well as directly from the folder, but as a subdomain appears to simply map a connection to a folder what difference could be expected?
There must be a link somewhere....
Posts: 1857
No, not necessarily. Depending on how you have everything set up, the htaccess in your root will also apply to all subfolders. There are sections that could possibly be ignored because of what's in a subfolder's htaccess file, but it will generally apply in at least some ways.
Difficult to comment without knowing what the two problems are. I'm assuming that these problems started when you put a second Gallery instance inside the first one and that they go away when you delete the second instance. Can't really think about it any more without more information about what's happening.
Subdomains don't necessarily work that way, UNLESS your host (or you) sets it up to work that way. Otherwise, subdomains are basically totally independent sites that do not overlap at all with the main domain.
Posts: 94
Many thanks for the subdomain clarification tempg.
As a result of this feedback I've now created subdomains for both of my test systems, one customised www.g3test.mydomain.co.uk with document root public_html/g3test, the other with no customisation www.g3trial.mydomain.co.uk with document root public_html/g3trial, both with no redirection.
Testing will only be done via these subdomains in future to investigate my problems with Search http://galleryproject.org/node/112155 and Module item_iframes http://galleryproject.org/node/108285 which still occur, even on the non customised system.