Ceon URI Mapping V5.0

It appears that some alterations are necessary when downloading the new 5.1.0 from Ceon's site and installing in Zen 1.5.7b. When I first installed 5.1.0 it crashed my site completely. I then applied Dr Byte's fix (https://www.zen-cart.com/showthread.php?225478-Ceon-URI-Mapping-V5-0&p=1377277#post1377277). After that I could get in to the back end but the front end did not work at all. I have disabled the plugin and the site works fine now.

I believe from previous posts that there is more necessary than what Dr Byte posted, but the information seems a little disjointed. Can someone please clarify what the changes are in one post?

http://winecountrycannabistours.com/
v 1.5.7b
(don't worry about looks, its R&D)

MasterRusty

masterrusty:

It appears that some alterations are necessary when downloading the new 5.1.0 from Ceon's site and installing in Zen 1.5.7b. When I first installed 5.1.0 it crashed my site completely. I then applied Dr Byte's fix (https://www.zen-cart.com/showthread.php?225478-Ceon-URI-Mapping-V5-0&p=1377277#post1377277). After that I could get in to the back end but the front end did not work at all. I have disabled the plugin and the site works fine now.

I believe from previous posts that there is more necessary than what Dr Byte posted, but the information seems a little disjointed. Can someone please clarify what the changes are in one post?

http://winecountrycannabistours.com/
v 1.5.7b
(don't worry about looks, its R&D)

MasterRusty
Might help to describe the history of the site... was a previous version installed to the fileset and then version 5.1.0 applied? Was this a new site that got version 5.1.0 installed? What logs were generated when enabled? All the fun things about getting help.

mc12345678:

Might help to describe the history of the site... was a previous version installed to the fileset and then version 5.1.0 applied? Was this a new site that got version 5.1.0 installed? What logs were generated when enabled? All the fun things about getting help.

Thank you for your help!

The zen portion of the site is fresh & clean Zen 1.5.7b. The database has data in it from Ceon URI going back to Zen 1.3.9. On my first try I had Ceon URI as the third plug I was installing and crashed. Tried removing retracing etc, no go. I backed out completely and installed everything other plugin we use, then went back to CEON URI. Then as described crashed until Dr. Byte's fix, but that just fixed the back end.

masterrusty:

Thank you for your help!

The zen portion of the site is fresh & clean Zen 1.5.7b. The database has data in it from Ceon URI going back to Zen 1.3.9. On my first try I had Ceon URI as the third plug I was installing and crashed. Tried removing retracing etc, no go. I backed out completely and installed everything other plugin we use, then went back to CEON URI. Then as described crashed until Dr. Byte's fix, but that just fixed the back end.

I had also tried installing Ceon URI as the first plug in during my troubleshooting. Here is a list of plugins as the site sits now:

Plugins:
Ceon URI 5.1.0 (nfg)
Cross Sell 1.5
EasyPopulate 4.0.36
Simplified Social Share 3.0
sitemapXML 3.9.6
Square 1.5
Image Handler 5.1.9

masterrusty:

Thank you for your help!

The zen portion of the site is fresh & clean Zen 1.5.7b. The database has data in it from Ceon URI going back to Zen 1.3.9. On my first try I had Ceon URI as the third plug I was installing and crashed. Tried removing retracing etc, no go. I backed out completely and installed everything other plugin we use, then went back to CEON URI. Then as described crashed until Dr. Byte's fix, but that just fixed the back end.
In the "installation" process, did the database update part get run from the admin? I don't recall the exact designation, but think it is: Modules->Ceon URI Mapping.

And I thought there was some other information in the documentation to address some problems. Not sure though here if the problems are with the software or the database. My last download of the 5.1.0 version appeared to have a fix already applied in the admin for the issue described...

I just did a complete site build, installed all of the files (not including template override files), accessed the modules section for the plugin, it did a complete install, went to the demo product section edited the category Software and saved it with a URI being auto-generated and then accessed it from the catalog/internet. Site is functional. I do did see the admin's deprecated issues that were recently identified. but I have no issues logged from the catalog and it is working.

As far as crashing, it is important to identify what went wrong... Blank screen, database error, file not placed correctly, whatever... May even need to download the plugin again just to be sure that everything made it in the file transfer...

mc12345678:

In the "installation" process, did the database update part get run from the admin? I don't recall the exact designation, but think it is: Modules->Ceon URI Mapping.

And I thought there was some other information in the documentation to address some problems. Not sure though here if the problems are with the software or the database. My last download of the 5.1.0 version appeared to have a fix already applied in the admin for the issue described...

I just did a complete site build, installed all of the files (not including template override files), accessed the modules section for the plugin, it did a complete install, went to the demo product section edited the category Software and saved it with a URI being auto-generated and then accessed it from the catalog/internet. Site is functional. I do did see the admin's deprecated issues that were recently identified. but I have no issues logged from the catalog and it is working.

As far as crashing, it is important to identify what went wrong... Blank screen, database error, file not placed correctly, whatever... May even need to download the plugin again just to be sure that everything made it in the file transfer...

Ok. So there is not a cumulative solution at this time. I apologize for being incomplete in my previous information I didn't want to repeat troubleshooting that had been done in previous posts.

The installation check says:
##################################################__
A file has had a modification made to it, for an older version of Ceon URI Mapping, but this modification is no longer needed.

The path to the file is /home/uzl677kjertd/public_html/a-com/includes/extra_datafiles/ceon_uri_mapping_sessions_define.php

• Although the file had to be modified for a previous version of the module, this version works differently and the file is not modified for this version.
• Remove the modification from the file by editing the file and removing the block beginning with // BEGIN CEON URI MAPPING 1 of 1 and ending with // END CEON URI MAPPING 1 of 1 - including those two “marker comments”.
  ##################################################

The file "/home/uzl677kjertd/public_html/a-com/includes/extra_datafiles/ceon_uri_mapping_sessions_define.php" on my server has no line that says "// BEGIN CEON URI MAPPING 1 of 1" (why would it? it is a ceon file).

When I turn on CEON URI in the admin links that use the "index.php?" format work. Links that use the CEON generated URI's result in a 404 error.

masterrusty:

Ok. So there is not a cumulative solution at this time. I apologize for being incomplete in my previous information I didn't want to repeat troubleshooting that had been done in previous posts.

The installation check says:
##################################################__
A file has had a modification made to it, for an older version of Ceon URI Mapping, but this modification is no longer needed.

The path to the file is /home/uzl677kjertd/public_html/a-com/includes/extra_datafiles/ceon_uri_mapping_sessions_define.php

• Although the file had to be modified for a previous version of the module, this version works differently and the file is not modified for this version.

• Remove the modification from the file by editing the file and removing the block beginning with // BEGIN CEON URI MAPPING 1 of 1 and ending with // END CEON URI MAPPING 1 of 1 - including those two “marker comments”.

##################################################

The file "/home/uzl677kjertd/public_html/a-com/includes/extra_datafiles/ceon_uri_mapping_sessions_define.php" on my server has no line that says "// BEGIN CEON URI MAPPING 1 of 1" (why would it? it is a ceon file).

When I turn on CEON URI in the admin links that use the "index.php?" format work. Links that use the CEON generated URI's result in a 404 error.
Well, looking at the installation instructions under

New files for the main store directory

I see this:
Note that the file includes/extra_datafiles/ceon_uri_mapping_sessions_define.php is not needed for a new installation.
and I don't see that file in the list of files to place on the server.

As far as upgrading (which one might think they are doing in this situation), the file seems to only be referenced in the sense that it should be removed when upgrading from certain versions of the plugin.

In all it doesn't look like the file does anything now, but did at one point. By that I mean, it doesn't look like there would be any harm of leaving that particular file other than the report provided in the installation check.

As to the 404 Error, there is information in the FAQs section: _docs/sections/faqs.html#rewrite-rule-missing-error

mc12345678:

Well, looking at the installation instructions under New files for the main store directory

I see this:
Note that the file includes/extra_datafiles/ceon_uri_mapping_sessions_define.php is not needed for a new installation.
and I don't see that file in the list of files to place on the server.

As far as upgrading (which one might think they are doing in this situation), the file seems to only be referenced in the sense that it should be removed when upgrading from certain versions of the plugin.

In all it doesn't look like the file does anything now, but did at one point. By that I mean, it doesn't look like there would be any harm of leaving that particular file other than the report provided in the installation check.

As to the 404 Error, there is information in the FAQs section: _docs/sections/faqs.html#rewrite-rule-missing-error

Looks like I followed the directions in the module and put the .htaccess file in public_html\a-com. I moved the commands from that file to the one in the public_html\ root and it seems to work now.

Thank you again.

Hi Guys,

I have just installed and having an issue where all URLs are working as expected except any urls of the base zencart set such as login, contact_us, shipping_info.

It seems to be failing on any url using the ?main_page= when clicking I am getting redirected to ?main_page=product_info&products_id=0

I am using Zencart 1.5.7b, CEON 5.1 umm edition from ceon.net

I am not getting any log files, I have tried this with both store template and default template with same issue.

I am not sure where to go or how to diagnose, Anyone have any ideas?

I have read the docs for any FAQs and also read this thread quite a bit.

DannyVarley:

Hi Guys,

I have just installed and having an issue where all URLs are working as expected except any urls of the base zencart set such as login, contact_us, shipping_info.

It seems to be failing on any url using the ?main_page= when clicking I am getting redirected to ?main_page=product_info&products_id=0

I am using Zencart 1.5.7b, CEON 5.1 umm edition from ceon.net

I am not getting any log files, I have tried this with both store template and default template with same issue.

I am not sure where to go or how to diagnose, Anyone have any ideas?

I have read the docs for any FAQs and also read this thread quite a bit.
Please post your /.htaccess file, the one that has all the ceon stuff in it

Here's what I currently have. I have tried it with just the CEON stuff I have tried adding a / in front of the index as described on the installation check page also.

###############################################################################
# Add custom headers and options
###############################################################################
# Notes:
#
# Examples: Adding IE compatibility / edge flags, language and encoding flags,
# php or suphp directives, configure other Apache modules such as page_speed,
# and enable or disable Apache httpd options.
#
# Do NOT configure anything directly relating to physical or virtual resources
# in this section. These should be addressed later on in this file.
###############################################################################
#Options -Indexes

###############################################################################
# Enable mod_rewrite processing using the rules in this .htaccess file
###############################################################################
# Notes:
#
# <IfModule> should be avoided at all costs. If mod_rewrite is not available
# it is almost always better to return HTTP 500 status. This way we see there
# is an issue as soon as the .htaccess file is uploaded.
#
# For mod_rewrite to work, the Apache server option to allow symbolic links to
# be followed must be enabled. Most providers supporting mod_rewrite will
# already have it enabled for you, but if your rewrite rules are not working
# you can un-comment the first directive below to manually enable the option.
#
# Don't forget, mod_rewrite directives are processed in order until a matching
# RewriteRule with the [L] flag is encountered. So the more specific a rule is
# the closer it should appear to the top of this file.
###############################################################################
#Options +FollowSymLinks
RewriteEngine on

###############################################################################
# Tell mod_rewrite where this file is relative to the server document_root
###############################################################################
# Notes:
#
# This directive should only be enabled if this .htaccess file is not placed
# in the document_root (usually public_html, www, or web) of the (sub)domain.
#
# An easy way to determine the location relative to the server document_root is
# to look at the URL used to access a file in this folder. For example if you
# access a "page" in the same folder as this file by typing in the URL
# "www.mydomain.com/myfolder/index.html" then "myfolder" will be the location
# of this file relative to the server document_root.
#
# Another quick and easy way to determine the correct setting for this is to
# look at the defined value for DIR_WS_CATALOG and DIR_WS_HTTPS_CATALOG in
# Zen Cart's configure.php files. All three values should match.
#
# Don't forget the leading and trailing /. This directive requires both!
###############################################################################
#RewriteBase /shop/


###############################################################################
# Redirect if request was for index.php (no query)
###############################################################################
# Notes:
#
# This is only required if the site generates references to index.php with no
# parameters. This rule will force a 301 redirect to the site root when a
# request is made for "/index.php" with no query terms (?key=value).
###############################################################################
#RewriteCond %{QUERY_STRING} ^$
#RewriteRule ^index\.php$ / [R=301,L]


###############################################################################
# Add any custom 301 redirects
###############################################################################
# Notes:
#
# In general these should be few and far between. If you use a RewriteRule
# be sure to add the L flag to let Apache mod_rewrite know to stop processing
# and skip any RewriteRules defined later in the .htaccess file.
###############################################################################


###############################################################################
# Redirect if request was for index.php (with or without query)
###############################################################################
# Notes:
#
# This is a performance optimization. If the request is for index.php simply
# pass the request on and do not process any other mod_rewrite directives in
# this file.
#
# Basically this avoids the overhead of checking if index.php is a real file
# or directory (used in subsequent mod_rewrite rules) before sending the
# request to index.php.
###############################################################################
RewriteRule ^index\.php$ - [L]

<IfModule mod_deflate.c>
  # Compress HTML, CSS, JavaScript, Text, XML and fonts
  AddOutputFilterByType DEFLATE application/javascript
  AddOutputFilterByType DEFLATE application/rss+xml
  AddOutputFilterByType DEFLATE application/vnd.ms-fontobject
  AddOutputFilterByType DEFLATE application/x-font
  AddOutputFilterByType DEFLATE application/x-font-opentype
  AddOutputFilterByType DEFLATE application/x-font-otf
  AddOutputFilterByType DEFLATE application/x-font-truetype
  AddOutputFilterByType DEFLATE application/x-font-ttf
  AddOutputFilterByType DEFLATE application/x-javascript
  AddOutputFilterByType DEFLATE application/xhtml+xml
  AddOutputFilterByType DEFLATE application/xml
  AddOutputFilterByType DEFLATE font/opentype
  AddOutputFilterByType DEFLATE font/otf
  AddOutputFilterByType DEFLATE font/ttf
  AddOutputFilterByType DEFLATE image/svg+xml
  AddOutputFilterByType DEFLATE image/x-icon
  AddOutputFilterByType DEFLATE text/css
  AddOutputFilterByType DEFLATE text/html
  AddOutputFilterByType DEFLATE text/javascript
  AddOutputFilterByType DEFLATE text/plain
  AddOutputFilterByType DEFLATE text/xml

  # Remove browser bugs (only needed for really old browsers)
  BrowserMatch ^Mozilla/4 gzip-only-text/html
  BrowserMatch ^Mozilla/4\.0[678] no-gzip
  BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
  Header append Vary User-Agent
</IfModule>

<ifModule mod_gzip.c>
mod_gzip_on Yes
mod_gzip_dechunk Yes
mod_gzip_item_include file .(html?|txt|css|js|php|pl)$
mod_gzip_item_include handler ^cgi-script$
mod_gzip_item_include mime ^text/.*
mod_gzip_item_include mime ^application/x-javascript.*
mod_gzip_item_exclude mime ^image/.*
mod_gzip_item_exclude rspheader ^Content-Encoding:.*gzip.*
</ifModule>

<ifModule mod_headers.c>
    Header set Connection keep-alive
</ifModule>


# ######################################################################
# # MEDIA TYPES AND CHARACTER ENCODINGS                                #
# ######################################################################

# ----------------------------------------------------------------------
# | Media types                                                        |
# ----------------------------------------------------------------------

# Serve resources with the proper media types (f.k.a. MIME types).
#
# https://www.iana.org/assignments/media-types/media-types.xhtml
# https://httpd.apache.org/docs/current/mod/mod_mime.html#addtype




# ----------------------------------------------------------------------
# | Reducing MIME type security risks                                  |
# ----------------------------------------------------------------------

# Prevent some browsers from MIME-sniffing the response.
#
# This reduces exposure to drive-by download attacks and cross-origin
# data leaks, and should be left uncommented, especially if the server
# is serving user-uploaded content or content that could potentially be
# treated as executable by the browser.
#
# http://www.slideshare.net/hasegawayosuke/owasp-hasegawa
# http://blogs.msdn.com/b/ie/archive/2008/07/02/ie8-security-part-v-comprehensive-protection.aspx
# https://msdn.microsoft.com/en-us/library/ie/gg622941.aspx
# https://mimesniff.spec.whatwg.org/

<IfModule mod_headers.c>
    Header set X-Content-Type-Options "nosniff"
</IfModule>

# ----------------------------------------------------------------------
# | ETags                                                              |
# ----------------------------------------------------------------------

# Remove `ETags` as resources are sent with far-future expires headers.
#
# https://developer.yahoo.com/performance/rules.html#etags
# https://tools.ietf.org/html/rfc7232#section-2.3

# `FileETag None` doesn't work in all cases.
<IfModule mod_headers.c>
    Header unset ETag
</IfModule>

FileETag None

# ----------------------------------------------------------------------
# | Expires headers                                                    |
# ----------------------------------------------------------------------

# Serve resources with far-future expires headers.
#
# (!) If you don't control versioning with filename-based
# cache busting, you should consider lowering the cache times
# to something like one week.
#
# https://httpd.apache.org/docs/current/mod/mod_expires.html

<IfModule mod_expires.c>

    ExpiresActive on
    ExpiresDefault                                      "access plus 1 month"

  # CSS
    ExpiresByType text/css                              "access plus 1 hour"

  # Data interchange
    ExpiresByType application/atom+xml                  "access plus 1 hour"
    ExpiresByType application/rdf+xml                   "access plus 1 hour"
    ExpiresByType application/rss+xml                   "access plus 1 hour"

    ExpiresByType application/json                      "access plus 0 seconds"
    ExpiresByType application/ld+json                   "access plus 0 seconds"
    ExpiresByType application/schema+json               "access plus 0 seconds"
    ExpiresByType application/vnd.geo+json              "access plus 0 seconds"
    ExpiresByType application/xml                       "access plus 0 seconds"
    ExpiresByType text/xml                              "access plus 0 seconds"

  # Favicon (cannot be renamed!) and cursor images
    ExpiresByType image/vnd.microsoft.icon              "access plus 1 year"
    ExpiresByType image/x-icon                          "access plus 1 year"

  # HTML
    ExpiresByType text/html                             "access plus 0 seconds"

  # JavaScript
    ExpiresByType application/javascript                "access plus 1 hour"
    ExpiresByType application/x-javascript              "access plus 1 hour"
    ExpiresByType text/javascript                       "access plus 1 hour"

  # Manifest files
    ExpiresByType application/manifest+json             "access plus 1 year"

    ExpiresByType application/x-web-app-manifest+json   "access plus 0 seconds"
    ExpiresByType text/cache-manifest                   "access plus 0 seconds"

  # Media files
    ExpiresByType audio/ogg                             "access plus 1 month"
    ExpiresByType image/bmp                             "access plus 1 month"
    ExpiresByType image/gif                             "access plus 1 month"
    ExpiresByType image/jpeg                            "access plus 1 month"
    ExpiresByType image/png                             "access plus 1 month"
    ExpiresByType image/svg+xml                         "access plus 1 month"
    ExpiresByType image/webp                            "access plus 1 month"
    ExpiresByType video/mp4                             "access plus 1 month"
    ExpiresByType video/ogg                             "access plus 1 month"
    ExpiresByType video/webm                            "access plus 1 month"

  # Web fonts
    # Embedded OpenType (EOT)
    ExpiresByType application/vnd.ms-fontobject         "access plus 1 month"
    ExpiresByType font/eot                              "access plus 1 month"

    # OpenType
    ExpiresByType font/opentype                         "access plus 1 month"

    # TrueType
    ExpiresByType application/x-font-ttf                "access plus 1 month"

    # Web Open Font Format (WOFF) 1.0
    ExpiresByType application/font-woff                 "access plus 1 month"
    ExpiresByType application/x-font-woff               "access plus 1 month"
    ExpiresByType font/woff                             "access plus 1 month"

    # Web Open Font Format (WOFF) 2.0
    ExpiresByType application/font-woff2                "access plus 1 month"

  # Other
    ExpiresByType text/x-cross-domain-policy            "access plus 1 week"

</IfModule>

## 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|woff2)$ [NC]
# Don't rewrite admin directory
RewriteCond %{REQUEST_URI} !^/backend [NC]
# Don't rewrite editors directory
RewriteCond %{REQUEST_URI} !^/editors/ [NC]
# Don't rewrite .htpasswds directory
RewriteCond %{REQUEST_URI} !^/\.htpasswds/ [NC]
# Don't rewrite .well-known directory
RewriteCond %{REQUEST_URI} !^/\.well\-known/ [NC]
# Don't rewrite bmz_cache directory
RewriteCond %{REQUEST_URI} !^/bmz_cache/ [NC]
# Don't rewrite min directory
RewriteCond %{REQUEST_URI} !^/min/ [NC]
# Don't rewrite pzen_includes directory
RewriteCond %{REQUEST_URI} !^/pzen_includes/ [NC]
# Don't rewrite logs directory
RewriteCond %{REQUEST_URI} !^/logs/ [NC]
# Don't rewrite zc_plugins directory
RewriteCond %{REQUEST_URI} !^/zc_plugins/ [NC]
# Handle all other URIs using Zen Cart (its index.php)
RewriteRule .* index.php [QSA,L]

## END CEON URI MAPPING REWRITE RULE

Hi Guys, Just an update on the above (This relates to the commercial UMM edition so I am not sure if this belongs here if not please feel free to let me know and I will remove the post)

I have the commercial manager edition of ceon purchased directly from ceon.net I have installed on a brand new clean install of 1.5.7b and I am having the same issue as above where main pages such as login or contact us are linked correctly, but when clicked on this goes to "main_page=product_info&products_id=0"

Steps to recreate

1. Download and install uri mappings umm edition
2. Download and install uri mappings manager
3. Create other pages urls using mappings manager
4. When clicking on the log-in page or any page using the main_page=**** it seems to direct to the "main_page=product_info&products_id=0"

Thanks,
Dan

DannyVarley:

Hi Guys, Just an update on the above (This relates to the commercial UMM edition so I am not sure if this belongs here if not please feel free to let me know and I will remove the post)

I have the commercial manager edition of ceon purchased directly from ceon.net I have installed on a brand new clean install of 1.5.7b and I am having the same issue as above where main pages such as login or contact us are linked correctly, but when clicked on this goes to "main_page=product_info&products_id=0"

Steps to recreate

1. Download and install uri mappings umm edition
2. Download and install uri mappings manager
3. Create other pages urls using mappings manager
4. When clicking on the log-in page or any page using the main_page=**** it seems to direct to the "main_page=product_info&products_id=0"

Thanks,
Dan
While not as easy in the version of the software described here in the forum, I checked one of the sites that use the free version where such an "other" page rewrite has been applied and it has the same problem...

So, following the bouncing ball and then comparing code of an older version to the 5.1.0 version, it looks like the issue is in:
includes/classes/class.CeonURIMappingHandler.php.
at or around line 159 is this:

$associated_db_id = (int)$mapping_info['associated_db_id']; 

It previously was:

$associated_db_id = $mapping_info['associated_db_id'];

and it looks like if that (int) casting were removed then the url wouldn't later get mischaracterized as a product like web address.

Not sure how that line number compares to the UMM version, but guessing that things are relatively similar...

mc12345678:

So, following the bouncing ball and then comparing code of an older version to the 5.1.0 version, it looks like the issue is in:
includes/classes/class.CeonURIMappingHandler.php.
at or around line 159 is this:

$associated_db_id = (int)$mapping_info['associated_db_id'];

> 
> It previously was:
> ```
$associated_db_id = $mapping_info['associated_db_id'];

and it looks like if that (int) casting were removed then the url wouldn't later get mischaracterized as a product like web address.

Not sure how that line number compares to the UMM version, but guessing that things are relatively similar...

Yep, This fixed it.

Thanks for the assist!

I am using zen cart 1.5.7 (not 1.5.7a or 1.5.7b). Will the 5.1.0 version work for me? Many thanks in advance!:smile:

markau:

I am using zen cart 1.5.7 (not 1.5.7a or 1.5.7b). Will the 5.1.0 version work for me? Many thanks in advance!:smile:
The answer is maybe. It will work **if **Ceon URI Mapping is the only additional code added to your store.

The un-suffixed zc157 has an error that disables the ability for multiple observers to act on the same event. See the bugfixes for the zc157 series for more information: https://www.zen-cart.com/showthread.php?226872-Known-bug-fixes-for-v1-5-7

lat9:

The answer is maybe. It will work **if **Ceon URI Mapping is the only additional code added to your store.

The un-suffixed zc157 has an error that disables the ability for multiple observers to act on the same event. See the bugfixes for the zc157 series for more information: https://www.zen-cart.com/showthread.php?226872-Known-bug-fixes-for-v1-5-7

Many thanks

markau:

I am using zen cart 1.5.7 (not 1.5.7a or 1.5.7b). Will the 5.1.0 version work for me? Many thanks in advance!:smile:

You REALLY need to upgrade ASAP. It's as simple as updating a handful of files.

ZC v1.5.7b
PHP v7.3.27
CSS/JS Loader
Dynamic Filter
CEON v5.1.0
OPC v2.3.4
DPU
Structured data
GDPR
Colorbox
Inventory
SitemapXML
IH5

Since upgrading CEON from v5.0.1 to v5.1.0 all of my rewritten pages (except category and product pages (I'm not using EZpages)) are redirecting to

/index.php?main_page=product_info&products_id=0 ('sorry, the product was not found')

I've double-checked the file uploads, tried PHP v7.2, the only change to the CEON .htaccess code was the addition of the plugins directory. No error logs. CEON installation check passed. There has been no change to the database entries for these pages they still read as this:

/privacy-policy | 1 | 1 | privacy | NULL | NULL | NULL | NULL | 2018-05-20 16:00:00

Any ideas why this might be happening or where to look?

simon1066:

ZC v1.5.7b
PHP v7.3.27
CSS/JS Loader
Dynamic Filter
CEON v5.1.0
OPC v2.3.4
DPU
Structured data
GDPR
Colorbox
Inventory
SitemapXML
IH5

Since upgrading CEON from v5.0.1 to v5.1.0 all of my rewritten pages (except category and product pages (I'm not using EZpages)) are redirecting to

/index.php?main_page=product_info&products_id=0 ('sorry, the product was not found')

I've double-checked the file uploads, tried PHP v7.2, the only change to the CEON .htaccess code was the addition of the plugins directory. No error logs. CEON installation check passed. There has been no change to the database entries for these pages they still read as this:

/privacy-policy | 1 | 1 | privacy | NULL | NULL | NULL | NULL | 2018-05-20 16:00:00

Any ideas why this might be happening or where to look?
Possibly see Post #193 as a solution that was posed for the same thing reported in Post #192.