conor:

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?

conor:

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

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: https://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

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

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

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....

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.

Thank you Paul69, that seems to make sense.

I'll give it a go

Cheers

Simon

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]

> 
> 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.

> **conor:**
>
> 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](http://dev.ceon.net/)

Hi,

simon1066:

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

Hi,

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

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

Thanks countrycharm and conor. I read a post where Dr Byte (I think it was) recommended a sub folder installation as the best way to go, he probably wasn't considering static URI's. As you recommend Conor, I'll go down the sub domain route. I'm a little confused as to what path to give the sub domain's directory.

Am I right in assuming that if I create the sudomain demo.mysite.com I can then use the default root cPanel's gives me, which is /public_html/demo, as the location for my files?

This doesn't seem right as this is the same location as a sub folder would have and I didn't think I wanted that.

Can't believe I'm so confused about this process - normally pretty good at this sort of thing.

cheers

Simon

Hi,

simon1066:

Thanks countrycharm and conor. I read a post where Dr Byte (I think it was) recommended a sub folder installation as the best way to go, he probably wasn't considering static URI's.

I didn't realise he'd said that.

Yes, he was clearly not considering sites that want to use static URIs.

simon1066:

As you recommend Conor, I'll go down the sub domain route. I'm a little confused as to what path to give the sub domain's directory.

It's a much nicer way to work.. it makes moving sites so much easier (e.g. from test to production).

simon1066:

Am I right in assuming that if I create the sudomain demo.mysite.com I can then use the default root cPanel's gives me, which is /public_html/demo, as the location for my files?

Yes, that's no problem.

simon1066:

This doesn't seem right as this is the same location as a sub folder would have and I didn't think I wanted that.

It's the same location in the file system but not the same "web-side" location.. the "root" of the demo.mysite.com site will be / not /demo and therefore the site's files can simply be moved to your production site's folder when you are ready to "change over".. the web server will serve the files from whichever directory is the base for a particular domain/subdomain independently of how they are positioned for other domains/subdomains on the same server.

All you then have to do is adjust configuration paths to remove the /demo and things will work instantly.. no need to adjust rewrite rules, URI mappings, image paths, CSS paths.. etc. etc.

I'm sure you can see the advantages! :)

simon1066:

Can't believe I'm so confused about this process - normally pretty good at this sort of thing.

Hopefully that helps? Everything's a learning process, that's something else under your belt, useful for the future! :)

All the best..

Conor
ceon

Conor, that's great. Thank you for taking the time to make things clear. I can move forward now.

Thanks

Simon

Hi,

It gives me great pleasure to annouce the availability of a new version of Ceon URI Mapping, v4.0.4.

This version makes it even easier to upgrade from pre-v4 versions and fixes a minor bug which only affects particular server setups.

As with all version 4.x releases, upgrading from a previous 4.x version is simple, taking no time at all, so everyone should upgrade!

From the Revision History:

[ADDED] Installation check extended to check if old files from a previous version of the software remain. It attempts to deletes any files/folder which should have been removed when upgrading. If the attempt at deletion is unsuccessful, it will warn the user about the presence of the old files/folder as they can conflict or even break the new/updated functionality.

[ADDED] Module will now make sure that its configuration group is added to the Zen Cart admin in 1.5.x.

[UPDATED] Styling of config utility interface improved with CSS3 graphical effects.

[UPDATED] Styling of fieldsets updated with code to fix problems with IE's rendering engine.

[BUGFIX] The code to manually build the $PHP_SELF server environment variable had a mistake in it. This could result in the software mistakenly disabling itself on particular server setups.

As always, the new version can be downloaded immediately from the Ceon website.

It has also been submitted to the Zen Cart downloads area and should be available there soon.

Enjoy!

All the best..

Conor
ceon

It gives me great pleasure to annouce the availability of a new version of Ceon URI Mapping, v4.0.4.

That's perfect timing, thanks Conor

simon1066:

That's perfect timing, thanks Conor

Cup of coffee and a doughnut on its way

Hi, I installed for the first time ceon, and gives me this error:
Database table can not be created! The user does not have database privileges CREATE TABLE!
thanks giancarlo

Conor, I've been using your URI mapper for sometime, and everything has worked perfect until today.

I added a new top level category with two sub-cats.

Now, I get a 403 error, just for those new categories.

All of the previous categories work fine.

When I turn off the CEON mapper, those new categories display correctly, along with all of the other categories.

Any ideas?

Thanks again for your hard work. :)

Hello

thanks for cool SEO mod, but there's something I don't know how to solve and I'm seeking for help. I am using ceon_uri_mapping_4.0.3_for_zc.zip with ZC 1.3.8a, with installed news and articles plugin by Dreamscape.

I do not know how to automatically generate seo-friendly urls with CEON mod. There is a new article going out around every second day and the database contains already 150 articles, which requires entering manually 150 entries into the ceo_uri_mappings mysql table.

My site is multilingual and I have to provide distinct URI for each language mutation, including the multilingual (en+cz) news and articles.

At the moment I am using Ultimate SEO URLs, which do not support unique multilingual URLs - there is one URL for both languages, which prevents indexing bots to distinguish between mutations and index secondary language pages.

I'd like to move to CEON URI Mapping, but I have no idea how to effectively add 150+ records for each news/article page.

Many thanks for any hints or ideas.

After upgrading to 4.0.4 from a new install of 4.0.3 that was working perfectly I received this error trying to load the Ceon URI Mapping (SEO) Config:

HTTP Error 500 (Internal Server Error)

The Debug file showes this:

[24-Sep-2011 23:37:21] PHP Warning: Cannot modify header information - headers already sent by (output started at /home/user/public_html/blank.com/admin/includes/languages/english/extra_definitions/ceon_uri_mapping.php:20) in /home/user/public_html/blank.com/admin/includes/init_includes/init_templates.php on line 28

Thanks