Quote Originally Posted by shags38 View Post
v1.5.7d ceon v5

I have recently built a new 1.5.7d site (treeoflifejewellery/newstore/dotcom) in a folder in the root of an existing v1.5.5f site (treeoflifejewellery.dotcom) - the intention is to develop that 1.5.7d and then change the website to that version.

The issue i'm having is that on the newly built site (treeoflifejewellery/newstore/dotcom) when I try to navigate to a product or a category it is taking me back the the existing site (treeoflifejewellery.dotcom). If I disable Ceon then navigation within the new site is fine.

The root has an access file with the Ceon rewrite instructions - to that I had to add RewriteCond %{REQUEST_URI} !^/newstore/ [NC] for the home page of newstore to open (otherwise a 404). If I add a .htaccess file to the newstore folder with the rewrite rules specific to that site (from the installation check page in Ceon) (and no other content) I get the existing site (treeoflifejewellery.dotcom) home page open and not newstore.

I assume the redirect issue will disappear when I replace the 'old' site with the new one as there won't be any conflicts however I would really like to prove the site first

So I am definitely missing something but not sure what it is - any help would be appreciated.

cheers, Mike
Well, there are those that I think will get at least a little chuckle out of *ME* saying this, but the above certainly is confusing. :)

Couple of thoughts to put together:
Your test site is a direct descendant of your live site.
Your live site has a set of rules that says, if the requested path matches (agrees with or doesn't agree with) the specific entries, then basically access the main site.
The module is effectively database driven. By copying the existing database to your test site, every existing link in that database is going to try to drive to the domain name of the site and whatever sub-directory associated with the database entry.
The instruction associated with the rules generated by the module indicate that those rules are for the root directory of the domain. It also basically says that there are multiple ways to obtain the desired end result.
The ideal method of "copying" an existing site to using this module is to establish a sub-domain (mytestsite.DOMAINNAME) that has the same sub-directory layout as your existing site. This is regardless of where that sub-site truly exists in relation to the main domain name.

So, you have a couple of options and a couple of paths to take.

My suggestion, besides placing this test site in maintenance mode, is to:
1) modify the original domain .htaccess file so that the existing rules will omit using/referencing your sub-directory path.
2) add the rules generated by the module *AFTER* your existing CEON URI rules.
3) Ensure that you *do not* have an .htaccess in the root of your test site (e.g. remove the .htaccess that was described in the above post).
4) BECAUSE THIS TEST SITE IS FOR VALIDATION PURPOSES AND IS NOT BEING USED TO CREATE NEW DATABASE RECORDS, update the database of your test site to concatenate the sub-directory path to the existing rewritten URI (meaning add the sub-directory path to the front) so that all of the URIs in the test site database point to some "tree" of your test site.

Doing the above, would support your test site links point to/reference the "test site" and the pages referenced from there.

Ideally, a sub-domain would be generated/used (updating the includes/configure.php and admin/includes/configure.php files). If that sub-domain was still in the above sub-directories, then your live site would have to redirect operation to the sub-domain directory via rules *before* your existing CEON URI rules, and then the generated CEON URI rules (after applying the sub-domain) would be placed within the sub-directory/root of that test site and the CEON URIs would not need to be modified... E.g. Less steps, but same/similar result.

After your test store has 1) received a copy of your live store database, and 2) been updated via zc_install, then
Within admin->Tools->Install SQL Patches
Code:
UPDATE ceon_uri_mapping SET uri = CONCAT('/newstore/dotcom', uri);
Do this once and only once *ASSUMING* you have not *yet* generated any links from within your test store.... If you have, then the above query would need to be modified to exclude the existence of any uri that begins with '/newstore/dotcom'....