Ceon URI Mapping v4.x

[mesnitu]

Ok, I know now it's something related with the product_book_info
If I insert a "regular" product it works fine.
Still don't remember what I've done.
Getting closer.
Thanks

[mc12345678]

Ok, I know now it's something related with the product_book_info
If I insert a "regular" product it works fine.
Still don't remember what I've done.
Getting closer.
Thanks

You should have done what is recommended (I think in the instructions) of updating: includes/extra_datafiles/ceon_uri_mapping_product_pages.php

To reflect the issue. So, there's the problem you were talking about, bookx product uris are not rewritten, but other product type are... easy fix and guiding to that file should help out. :)

[mesnitu]

Well, one of those days....what can I say.
I even wrote what to do 2 years ago

https://github.com/mesnitu/Ceon-Book...xtra_datafiles

This as to be Karma!

[lat9]

Any pointers for running the Ceon URI Mapping on a localhost installation? I've got an XAMPP installation on my computer and normally access my test installations as http[s]://localhost/store_name.

When I've got a store that uses the URI mappings, any mapping generated discards the store_name portion of the link resulting in 404's. I'm expecting that the generated links should be localhost/store_name/the_link, but they're coming out as simply localhost/the_link.

[mc12345678]

How is you're HTTP_HOST and/or DIR_WS_CATALOG defined?

How/where is the .htaccess that was recommended by the install and is there one in the sub-directory (if so please provide contents of both omitting/obscuring the admin directory RewriteCond for it and the comment above it.)

[lat9]

Thanks for the prompt response, @mc12345678. The information you requested:

HTTP_SERVER is http://localhost
DIR_WS_CATALOG is /store_name/

.htaccess (located in the root of the /store_name directory):

## BEGIN CEON URI MAPPING REWRITE RULE

RewriteEngine On
# Don't rewrite any URIs ending with a file extension (ending with .[xxxxx])
RewriteCond %{REQUEST_URI} !\.[a-z]{2,5}$ [NC]
# Don't rewrite any URIs for some, popular specific file format extensions,
#   which are not covered by main file extension condition above
RewriteCond %{REQUEST_URI} !\.(mp3|mp4|h264)$ [NC]
# Don't rewrite any URIs for some specific file format extensions,
#   which are not covered by main file extension condition above
#   Uncomment the following line to apply this condition! (Remove the # at the start of the next line)
#RewriteCond %{REQUEST_URI} !\.(3gp|3g2|h261|h263|mj2|mjp2|mp4v|mpg4|m1v|m2v|m4u|f4v|m4v|3dml)$ [NC]
# Don't rewrite admin directory
RewriteCond %{REQUEST_URI} !^/admin [NC]
# Don't rewrite editors directory
RewriteCond %{REQUEST_URI} !^/editors/ [NC]
# Don't rewrite logs directory
RewriteCond %{REQUEST_URI} !^/logs/ [NC]
# Don't rewrite sitemap directory
RewriteCond %{REQUEST_URI} !^/sitemap/ [NC]
# Don't rewrite cgi-bin directory
RewriteCond %{REQUEST_URI} !^/cgi\-bin/ [NC]
# Handle all other URIs using Zen Cart (its index.php)
RewriteRule .* index.php [QSA,L]

## END CEON URI MAPPING REWRITE RULE

[mc12345678]

What's the plan for any uris generated in the local environment related to an online site? Ie. Will that site have the same sub-folder structure, will it be another directory name, or is neither of that a factor?Ask because can possibly provide a local "only" solution or one that supports moving this htaccess elsewhere. Mind you, the instructions recommend that the htaccess be placed in the root of the domain (paraphrasing) such that it would have been expected to be at localhost not localhost/store_name from the web-facing address.

[lat9]

What's the plan for any uris generated in the local environment related to an online site? Ie. Will that site have the same sub-folder structure, will it be another directory name, or is neither of that a factor?Ask because can possibly provide a local "only" solution or one that supports moving this htaccess elsewhere. Mind you, the instructions recommend that the htaccess be placed in the root of the domain (paraphrasing) such that it would have been expected to be at localhost not localhost/store_name from the web-facing address.

I'm not totally sure what you're asking. My expectation is that any URIs generated are relative to the site's current installation.

That is if the ceon-generated URI is microsoft-intellimouse-pro, my expectation is that the localhost'd version would be http://localhost/store_name/microsoft-intellimouse-pro while the webhosted version would be http://www.store_name.com/microsoft-intellimouse-pro (since the site's hosted version is in the root of the hosted account).

[paul3648]

I have this working by setting up my install folder as an apache2 virtual host, then putting the CEON mappings directly in the conf file of /etc/apache2/vhosts.d folder.

So rather than accessing it as http://localhost/myinstall I access it as http://myinstall

[simon1066]

Any pointers for running the Ceon URI Mapping on a localhost installation? I've got an XAMPP installation on my computer and normally access my test installations as http[s]://localhost/store_name.

When I've got a store that uses the URI mappings, any mapping generated discards the store_name portion of the link resulting in 404's. I'm expecting that the generated links should be localhost/store_name/the_link, but they're coming out as simply localhost/the_link.

Not sure what pointers you need but I have my local dev copies of ZC running on a windows pc (uniformserver), this is the way I've done it and apologies in advance if I'm teaching you to suck eggs:

by editing the windows etc/hosts file I access the dev site just by using example.com - no localhost to worry about and this means my URI's are the same as my live site. Of course this means I can't access the live site on this PC without changing the hosts file, which is fine as I have another PC for live site access.

my CEON htaccess (root) content is the same as yours.

my includes/configure.php is

define('HTTP_SERVER', 'https://example.com');
define('HTTPS_SERVER', 'https://example.com');
define('DIR_WS_CATALOG', '/');
define('DIR_WS_HTTPS_CATALOG', '/');
define('DIR_FS_CATALOG', 'C:/server/UniserverZ/www/example.com/');

Hope this helps.