Ceon URI Mapping v4.x

[Semenek]

Make sure that you have the correct settings for the HTTP_SERVER/HTTPS_SERVER/HTTP_CATALOG_SERVER etc. variables.

Then make sure that if you have any extra rewrite rules in your .htaccess file, other than the Ceon URI Mapping one, that they match up with what you have set in your configure.php files.

Conor
ceon

I checked configure.php and all my additional redirects.

BUT,
I modified .htaccess file so many time trying to fix the problem, so I lost original file. I download the CEON plugin again, but could not find .htaccess file. Can you please tell me where I can get the "original" version of rewrite rules for CEON?

Finally, once you've done all the above, if you still have add to cart issues then you haven't modified html_output.php.

Conor
ceon

And, where I can find html_output.php file?



Thanks, Elena

[simon1066]

My current task is to upgrade my store from 1.3.8a to 1.3.9h

I'm having difficulty using zc_install to install a demo version of 1.3.9h into a sub-directory: www.mysite.com/demo/ due to these lines in my .htaccess file

# Don't rewrite any URIs ending with a file extension (ending with .[xxxx])
RewriteCond %{REQUEST_URI} !\.[a-zA-Z]{2,4}$
# Don't rewrite admin directory
RewriteCond %{REQUEST_URI} !^/admin_1700.* [NC]
# Don't rewrite editors directory
RewriteCond %{REQUEST_URI} !^/editors.* [NC]
# Don't rewrite payment pages/callback handlers
# (Won't be rewritten by rules above but included here in case rewriting of URIs ending in .php is added)
RewriteCond %{REQUEST_URI} !^/ipn_main_handler.php.* [NC]
RewriteCond %{REQUEST_URI} !^/iridium_3d_secure_iframe.php.* [NC]
RewriteCond %{REQUEST_URI} !^/localities_remote_loader.php.* [NC]
RewriteCond %{REQUEST_URI} !^/nochex_apc_handler.php.* [NC]
RewriteCond %{REQUEST_URI} !^/protx_direct_3d_secure_iframe.php.* [NC]
RewriteCond %{REQUEST_URI} !^/realex_remote_3d_secure_iframe.php.* [NC]
# Don't rewrite blog directories
RewriteCond %{REQUEST_URI} !/blog.* [NC]
# Don't rewrite cPanel directories
RewriteCond %{REQUEST_URI} !/cpanel.* [NC]
RewriteCond %{REQUEST_URI} !/frontend.* [NC]
# Handle all other URIs using Zen Cart (index.php)
RewriteRule (.*) index.php?%{QUERY_STRING} [L]

The plan is to get my existing site up and running in the demo folder, on 1.3.9h, before going live with it.

I've seen reference to the fact that the CEON .htaccess rules prohibit the use of zc_install but cannot find a solution.

I'm thinking that I temporarily remove the above lines from .htaccess until I've been through the zencart install process. Is this the recommended way? Will the above lines of code cause problems with the future operation of my 'demo' store?

One post referred to upgrading through the individual zencart upgrades one by one from 1.3.8a to 1.3.9h, I suppose one might then be able to work on the 'live' site without too much interruption. This seems like a lot more work and given that I have CEON mapping just the way I want it and that I have numerous other mods installed, is this a better way of upgrading than jumping straight from 8a to 9h?

Thanks

Simon

[simon1066]

I decided to try this

I'm thinking that I temporarily remove the above lines from .htaccess until I've been through the zencart install process. Is this the recommended way? Will the above lines of code cause problems with the future operation of my 'demo' store?

Zencart installs in sub directory, but is inaccessible when restoring the .htaccess back to its original state. Seems like I need to make a change to this file to allow sub-directory store access AND keep the full functionality of CEON mapping in my existing store, suggestions?

Thanks

Simon

[simon1066]

Seems that if I delete this rule

# Handle all other URIs using Zen Cart (index.php)
RewriteRule (.*) index.php?%{QUERY_STRING} [L]

then I'm able to access zen cart installed in a sub folder, but this breaks my existing site, url mapping-wise.

Unfortunately I'm not knowledgeable enough to understand what this rule does or how to get around thie problem

[Paul69]

I believe you can re run the ceon installation check and it will auto generate the htaccess info again in its current directory. I have a test site and live site running both with the test on a subdirectory configured as a sub domain. It seems to work for both ok. Go under the module menu and select the ceon uri and go to the installation check. Now go to the installation check page and you should see it. Hope that helps....

[Paul69]

Forgot to add you cannot duplicate the htaccess file in a subdirectry you can only update the top level to include the rewrite rules for both.

[simon1066]

Thank you Paul69, that seems to make sense.

I'll give it a go

Cheers

Simon

[countrycharm]

My current task is to upgrade my store from 1.3.8a to 1.3.9h

I'm having difficulty using zc_install to install a demo version of 1.3.9h into a sub-directory: www.mysite.com/demo/ due to these lines in my .htaccess file

# Don't rewrite any URIs ending with a file extension (ending with .[xxxx])
RewriteCond %{REQUEST_URI} !\.[a-zA-Z]{2,4}$
# Don't rewrite admin directory
RewriteCond %{REQUEST_URI} !^/admin_1700.* [NC]
# Don't rewrite editors directory
RewriteCond %{REQUEST_URI} !^/editors.* [NC]
# Don't rewrite payment pages/callback handlers
# (Won't be rewritten by rules above but included here in case rewriting of URIs ending in .php is added)
RewriteCond %{REQUEST_URI} !^/ipn_main_handler.php.* [NC]
RewriteCond %{REQUEST_URI} !^/iridium_3d_secure_iframe.php.* [NC]
RewriteCond %{REQUEST_URI} !^/localities_remote_loader.php.* [NC]
RewriteCond %{REQUEST_URI} !^/nochex_apc_handler.php.* [NC]
RewriteCond %{REQUEST_URI} !^/protx_direct_3d_secure_iframe.php.* [NC]
RewriteCond %{REQUEST_URI} !^/realex_remote_3d_secure_iframe.php.* [NC]
# Don't rewrite blog directories
RewriteCond %{REQUEST_URI} !/blog.* [NC]
# Don't rewrite cPanel directories
RewriteCond %{REQUEST_URI} !/cpanel.* [NC]
RewriteCond %{REQUEST_URI} !/frontend.* [NC]
# Handle all other URIs using Zen Cart (index.php)
RewriteRule (.*) index.php?%{QUERY_STRING} [L]

The plan is to get my existing site up and running in the demo folder, on 1.3.9h, before going live with it.

I've seen reference to the fact that the CEON .htaccess rules prohibit the use of zc_install but cannot find a solution.

I'm thinking that I temporarily remove the above lines from .htaccess until I've been through the zencart install process. Is this the recommended way? Will the above lines of code cause problems with the future operation of my 'demo' store?

One post referred to upgrading through the individual zencart upgrades one by one from 1.3.8a to 1.3.9h, I suppose one might then be able to work on the 'live' site without too much interruption. This seems like a lot more work and given that I have CEON mapping just the way I want it and that I have numerous other mods installed, is this a better way of upgrading than jumping straight from 8a to 9h?

Thanks

Simon

Sub Domains are the only way to go when installing this module. It can not be in a test folder.

Hi,



Installing the software on a site that uses subdomains is the recommended way to implement the software. The software doesn't care what domain/subdomain it's on but the *web-side folder/path* the site is in is critical.

Sites using the same folder/DIR_WS_CATALOG are 100% compatible regardless of what subdomain is being used.. this is a big reason why subdomains are the professional way to create test/development sites.



Sounds like you've something else in your .htaccess which is messing up. Bad flags errors cannot be generated by the example rewrite rule generated by Ceon URI Mapping.

Fix any problems in your .htaccess file and use the example rewrite rule from the installation check and all should be fine.

All the best...

Conor
ceon

[conor]

Hi,

I'm having difficulty using zc_install to install a demo version of 1.3.9h into a sub-directory: www.mysite.com/demo/

You CANNOT install a demo or test site in a subdirectory when building a site with static URIs.. It's an unprofessional way to develop.

Use a subdomain or another domain.

That's it.. that's the solution.. don't bother with anything else, it's just hassle (doable but hassle - I won't help with such a solution ;) ).

All the URIs will be wrong for a subdirectory site, they won't work when you want to use it as a live site (again without hassle that is).

All the best..

Conor
ceon

[conor]

Hi,

I believe you can re run the ceon installation check and it will auto generate the htaccess info again in its current directory. I have a test site and live site running both with the test on a subdirectory configured as a sub domain

Yes.. running the sites as subdomains is the perfect, professional way to go.. good stuff! :)

As long as the "web side" of things isn't built around a subdirectory (site.com/demo), like simon1066 was mistakenly trying to do.

The physical directories the sites are in don't matter, it's the web-side structure that messes up static URI sites.. subdomains avoid those problems.

All the best...

Conor
ceon