Ceon URI Mapping V5.0

shags38:

Hello mc12345678 - so I did search the other day when you mentioned that you thought a 5.1.0 version was available however I didn't find it - I have searched again subsequent to your response above and to no avail - searched within ZC Plugins using various keywords and also did a Google search. If you manage to stumble upon it again then a link to it in here would be appreciated.

The latest version of CEON URI Mapping (v5.1.0) is available on CEON's website at https://ceon.net/seo-modules/ceon-uri-mapping-seo

You could be forgiven for thinking that the version is actually v5.0, but if you download the zip you'll find it's v5.1.0 within. The revision history in the subsequent docs shows 13 Dec 2020 as the release date for v5.1.0

simon1066:

The latest version of CEON URI Mapping (v5.1.0) is available on CEON's website at https://ceon.net/seo-modules/ceon-uri-mapping-seo

You could be forgiven for thinking that the version is actually v5.0, but if you download the zip you'll find it's v5.1.0 within. The revision history in the subsequent docs shows 13 Dec 2020 as the release date for v5.1.0

simon1066 - thanks mate for the information and for posting that link :smile: - I have downloaded that version and will now read all the docs before installing.

again many thanks,
Mike

I installed version 5.1.0 this morning after reading the documentation and following it to the letter - after install I could not get to my admin, page returned a 500 error (cannot be accessed on this server)- the site was live however. I read the ZC document on the probable causes and remedies. Server mod_security was likely so I contacted my host and after investigation they said it was not a mod_security. Ceon docs suggested putting a / in front of index.php in the .htaccess file, but that didn't work.

So I reloaded version 5.0.0 and removed all residual files from version 5.1.0 (eventually).

Now I can get both admin and the site up - but as soon as I turn ceon to on I lose the website (cannot access - too many redirects) the .htaccess in the root is exactly as it was yesterday prior to the attempted upgrade

There were a couple of myDEBUG errors that showed up at different stages of me trying to get ceon to work - these remain;

this was the second last error, showed up a few times at various stages of me trying to sort this out - I did a winmerge file comparison of installed to my downlaoded file in my drive (and even re-downloaded version 5.0.0 to be certain the file wasn't corrupted during original download) - the files are exactly the same. Again I don't think this file is responsible mainly because the I used a back up site copy from prior to doing the 5.1.0 install (admin and include folders and database copy) - so everything is as it was yesterday.

[27-Jan-2021 15:10:10 Australia/Sydney] PHP Parse error: syntax error, unexpected '$this' (T_VARIABLE), expecting ';' or '{' in /dazzlers/includes/classes/observers/class.CeonURIMappingLinkBuildAdmin.php on line 61

[27-Jan-2021 15:10:10 Australia/Sydney] Request URI: /dazzlers/index.php, IP address: 115.166.19.58
--> PHP Parse error: syntax error, unexpected '$this' (T_VARIABLE), expecting ';' or '{' in /dazzlers/includes/classes/observers/class.CeonURIMappingLinkBuildAdmin.php on line 61.

this is the last error to show however I do not think it is responsible for the website not being available for the reason that I was getting this error yesterday when still using v5.0.0 (see post #157);

[27-Jan-2021 15:59:12 Australia/Sydney] Request URI: /dazzlers/index.php?cmd=orders&origin=index&page=1&oID=552&action=update_order&language=en, IP address: 115.166.19.58
#1 CeonURIMappingLinkBuildAdmin->updateNotifySEFUInterceptAdmcathref() called at [/includes/classes/class.base.php:118]
#2 base->notify() called at [/dazzlers/includes/functions/html_output.php:71]
#3 zen_catalog_href_link() called at [/includes/functions/functions_osh_update.php:119]
#4 zen_update_orders_history() called at [/dazzlers/orders.php:254]
#5 require(/dazzlers/orders.php) called at [/dazzlers/index.php:11]
--> PHP Warning: Use of undefined constant ENABLE_SSL - assumed 'ENABLE_SSL' (this will throw an Error in a future version of PHP) in /dazzlers/includes/classes/observers/class.CeonURIMappingLinkBuildAdmin.php on line 46.

[27-Jan-2021 15:59:12 Australia/Sydney] Request URI: /dazzlers/index.php?cmd=orders&origin=index&page=1&oID=552&action=update_order&language=en, IP address: 115.166.19.58
#1 CeonURIMappingLinkBuildAdmin->updateNotifySEFUInterceptAdmcathref() called at [/includes/classes/class.base.php:118]
#2 base->notify() called at [/dazzlers/includes/functions/html_output.php:71]
#3 zen_catalog_href_link() called at [/includes/functions/functions_osh_update.php:136]
#4 zen_update_orders_history() called at [/dazzlers/orders.php:254]
#5 require(/dazzlers/orders.php) called at [/dazzlers/index.php:11]
--> PHP Warning: Use of undefined constant ENABLE_SSL - assumed 'ENABLE_SSL' (this will throw an Error in a future version of PHP) in /dazzlers/includes/classes/observers/class.CeonURIMappingLinkBuildAdmin.php on line 46.

[27-Jan-2021 15:59:12 Australia/Sydney] Request URI: /dazzlers/index.php?cmd=orders&origin=index&page=1&oID=552&action=update_order&language=en, IP address: 115.166.19.58
#1 CeonURIMappingLinkBuildAdmin->updateNotifySEFUInterceptAdmcathref() called at [/includes/classes/class.base.php:118]
#2 base->notify() called at [/dazzlers/includes/functions/html_output.php:71]
#3 zen_catalog_href_link() called at [/includes/languages/english/modules/payment/paypalwpp.php:19]
#4 require_once(/includes/languages/english/modules/payment/paypalwpp.php) called at [/dazzlers/orders.php:268]
#5 require(/dazzlers/orders.php) called at [/dazzlers/index.php:11]
--> PHP Warning: Use of undefined constant ENABLE_SSL - assumed 'ENABLE_SSL' (this will throw an Error in a future version of PHP) in /dazzlers/includes/classes/observers/class.CeonURIMappingLinkBuildAdmin.php on line 46.

So I am stuck with dynamic urls with a bunch of products to add to the site - any assistance will be appreciated.

cheers,
Mike

Well, I know I'm completely confused about 1) the current state of installation, 2) what the state really was yesterday, and 3) what the real problem is/was when the software was installed...

Want some assistance? Pretty much the same thing that is and has always been suggested everytime that you have had a 500 error and/or blank screen reported with anything that has been done...

Allow me to ask, what is the recommended action to identify what went wrong when a 500 error or blank page occurs?

shags38:

I installed version 5.1.0 this morning after reading the documentation and following it to the letter

[27-Jan-2021 15:10:10 Australia/Sydney] PHP Parse error: syntax error, unexpected '$this' (T_VARIABLE), expecting ';' or '{' in /dazzlers/includes/classes/observers/class.CeonURIMappingLinkBuildAdmin.php on line 61

There's a serious bug in the 5.1.0 version of that file (and maybe 5.0.0 too, I dunno).
You need to insert a new line at line 61, containing just this:

{

> **shags38:**
>
> ```
PHP Warning: Use of undefined constant ENABLE_SSL - assumed 'ENABLE_SSL' (this will throw an Error in a future version of PHP) in /dazzlers/includes/classes/observers/class.CeonURIMappingLinkBuildAdmin.php on line 46.

The 5.1.0 version of that file mentions ENABLE_SSL_CATALOG, not ENABLE_SSL.
So I suspect those warnings came from the old version, and therefore are no longer occurring?

shags38:

Now I can get both admin and the site up - but as soon as I turn ceon to on I lose the website (cannot access - too many redirects) the .htaccess in the root is exactly as it was yesterday prior to the attempted upgrade

Like @mc12345678 I'm unsure of the current state of play, but if you have v5.0.0 installed with the above issue then the fix for this is in this post - https://www.zen-cart.com/showthread.php?225478-Ceon-URI-Mapping-V5-0&p=1359888#post1359888.

This was fixed in v5.0.1, although you probably don't have access to that as it was only available on CEON's website and has since been superseded by v5.1.0

simon1066:

Like @mc12345678 I'm unsure of the current state of play, but if you have v5.0.0 installed with the above issue then the fix for this is in this post - https://www.zen-cart.com/showthread.php?225478-Ceon-URI-Mapping-V5-0&p=1359888#post1359888.

This was fixed in v5.0.1, although you probably don't have access to that as it was only available on CEON's website and has since been superseded by v5.1.0

Many thanks Simon - that did the trick - I am now as funtional with 5.0.0 as I was before attempting upgrade to 5.1.0.

Now to try 5.1.0 again maybe?

I really do appreciate your help.

cheers,
Mike

shags38:

Many thanks Simon - that did the trick - I am now as funtional with 5.0.0 as I was before attempting upgrade to 5.1.0.

Now to try 5.1.0 again maybe?

I really do appreciate your help.

cheers,
Mike

It does make sense to upgrade to v5.1.0 (I'm still on v5.0.1 so haven't tried it yet). Not sure if you do this already but I would recommend running a development copy of your site locally on your PC/Mac. You can test out upgrades before you go live - particularly useful for the larger more compicated mods like this one.

simon1066:

It does make sense to upgrade to v5.1.0 (I'm still on v5.0.1 so haven't tried it yet). Not sure if you do this already but I would recommend running a development copy of your site locally on your PC/Mac. You can test out upgrades before you go live - particularly useful for the larger more compicated mods like this one.

So Simon if you are using 5.0.1 do you have the issue that I was speaking about from the start? .i.e. when adding a new product even with auto generate uri mapping ticked and then clicking preview, if you click << back to revise something upon clicking preview again the uri mapping disappears and if you update the product it uses ZC generated urls and not ceon?

Yes I should be using a development site - will create one tomorrow (nearly midnight here now) and try Ceon v5.1.0 in there and see what transpires. I'm just wondering if anyone at all has got 5.1.0 successfully working on 1.5.7b ??

shags38:

So Simon if you are using 5.0.1 do you have the issue that I was speaking about from the start? .i.e. when adding a new product even with auto generate uri mapping ticked and then clicking preview, if you click << back to revise something upon clicking preview again the uri mapping disappears and if you update the product it uses ZC generated urls and not ceon?

Yes, I do. With CEON v5.0.1 / ZC v1.5.7b or ZC v1.5.6c. I hadn't noticed it before, as I rarely hit 'back' after 'preview'. If it hasn't been previously addressed in this thread perhaps it has been resolved in CEON v5.1.0. A workaround would be to save the product (click insert) and then go back into the product again to edit.

simon1066:

Yes, I do. With CEON v5.0.1 / ZC v1.5.7b or ZC v1.5.6c. I hadn't noticed it before, as I rarely hit 'back' after 'preview'. If it hasn't been previously addressed in this thread perhaps it has been resolved in CEON v5.1.0. A workaround would be to save the product (click insert) and then go back into the product again to edit.

Thanks for your response Simon - it validates at least to me that the issue I am having is not of my doing :smile: I agree with the workaround you suggested except that if in the product revision you make a change to the title of the product then the originally generated url remains and doesn't change to the newly modified title - and as far as I am aware you can't manually change CEON url's after they have been generated ....... and yes maybe it has been addressed in v5.1.0 (if anyone had reported it as an issue) however I cannot get v5.1.0 to work, hence the dilemma :smile:

Again thanks for your response.

cheers,
Mike

shags38:

Thanks for your response Simon - it validates at least to me that the issue I am having is not of my doing :smile: I agree with the workaround you suggested except that if in the product revision you make a change to the title of the product then the originally generated url remains and doesn't change to the newly modified title - and as far as I am aware you can't manually change CEON url's after they have been generated ....... and yes maybe it has been addressed in v5.1.0 (if anyone had reported it as an issue) however I cannot get v5.1.0 to work, hence the dilemma :smile:

Again thanks for your response.

cheers,
Mike
ABSOLUTELY the uri can be modified after it has been entered and/or auto-generated! That's one of the points of the software... IF you keep the ceon database tables that is. To do that? When updating the store, follow the Zen Cart process(es).

I checked back to the ZC 1.5.7b site where I had installed the 5.1.0 version and it would appear that in addressing issues with whatever software was being installed, that I had independently applied the fix that DrByte mentioned above. Sorry for not recognizing the issue, for what I was dealing with it was one minor one of many other issues.

That said, I asked them to repeat the action of initiating a product, going to preview and then returning back and it seems like it works like it always does or has. Further it looks like the cause of that craziness is because of changes that were made to the buttons in the product review process where the cancel/back button uses a different link now than it used to use...

mc12345678:

ABSOLUTELY the uri can be modified after it has been entered and/or auto-generated! That's one of the points of the software... IF you keep the ceon database tables that is. To do that? When updating the store, follow the Zen Cart process(es).

I checked back to the ZC 1.5.7b site where I had installed the 5.1.0 version and it would appear that in addressing issues with whatever software was being installed, that I had independently applied the fix that DrByte mentioned above. Sorry for not recognizing the issue, for what I was dealing with it was one minor one of many other issues.

That said, I asked them to repeat the action of initiating a product, going to preview and then returning back and it seems like it works like it always does or has. Further it looks like the cause of that craziness is because of changes that were made to the buttons in the product review process where the cancel/back button uses a different link now than it used to use...

Thanks MC - I have created a development site so will try installing v5.1.0 in there soon, after I get all these products loaded :smile: I searched CEON FAQ's and other sections of the plugin docs and didn't find anything regarding retrospectively changing generated url's, maybe I skimmed too quickly - I have the ceon database tables so I assume you make any changes directly in the database tables?

cheers,
Mike

shags38:

Thanks MC - I have created a development site so will try installing v5.1.0 in there soon, after I get all these products loaded :smile: I searched CEON FAQ's and other sections of the plugin docs and didn't find anything regarding retrospectively changing generated url's, maybe I skimmed too quickly - I have the ceon database tables so I assume you make any changes directly in the database tables?

cheers,
Mike
For normal use and everyday action, enter in the admin whatever address you want to use for the product. Whatever is last added is what will be the current address. Any previously entered address will go to the current address.

Sure from an outside perspective you don't necessarily want to frequently change the address of the product, but there is nothing wrong with some sort of change. Further, because an entered address goes to the same place throughout time, any address to that product is only a single redirect away and not complicated as if/when trying to do a bunch of redirects in an .htaccess.

Basically, stop overthinking things. You've been doing this stuff long enough to at least address the simple things. While the message may have changed or the help document location may have changed, its still the same thing and that troubleshooting doesn't really matter whether it is here or in some other software. It's just really easy here to identify, review and correct the issues. Some software lucky to find the log that identifies what the last big problem was...

shags38:

Thanks for your response Simon - it validates at least to me that the issue I am having is not of my doing :smile: I agree with the workaround you suggested except that if in the product revision you make a change to the title of the product then the originally generated url remains and doesn't change to the newly modified title - and as far as I am aware you can't manually change CEON url's after they have been generated ....... and yes maybe it has been addressed in v5.1.0 (if anyone had reported it as an issue) however I cannot get v5.1.0 to work, hence the dilemma :smile:

Again thanks for your response.

cheers,
Mike

I know @mc12345678 has helped with this but just in case you are still having difficulty generating a new URI for a product once the title has been altered (and at the risk of teaching you how to suck eggs):

If I edit a product in admin, change the title, at the bottom of the screen I see this:

Just make sure the box is ticked then Preview and Update as normal to get a new URI. If you don't want to use an auto-generated URI, then just edit the URI field and leave the box unticked.

simon1066:

I know @mc12345678 has helped with this but just in case you are still having difficulty generating a new URI for a product once the title has been altered (and at the risk of teaching you how to suck eggs):

If I edit a product in admin, change the title, at the bottom of the screen I see this:

Just make sure the box is ticked then Preview and Update as normal to get a new URI. If you don't want to use an auto-generated URI, then just edit the URI field and leave the box unticked.
For what I expect to be clarity of the above, if an object such as a product already has a rewrite, then I would expect the above image but with one minor difference that the checkbox would not be (automatically) checked. I would expect it to be auto-checked only if the product does not have a rewrite and that checkbox is defaulted to be on through the settings of the module.

Otherwise I would expect the above to be accurate... name change followed by checking that block and moving through the save aspect would cause a new rewrite to match the new name and whatever other settings there are. At least unless that new rewrite matches any that have previously existed...

mc12345678:

For what I expect to be clarity of the above, if an object such as a product already has a rewrite, then I would expect the above image but with one minor difference that the checkbox would not be (automatically) checked. I would expect it to be auto-checked only if the product does not have a rewrite and that checkbox is defaulted to be on through the settings of the module.

Otherwise I would expect the above to be accurate... name change followed by checking that block and moving through the save aspect would cause a new rewrite to match the new name and whatever other settings there are. At least unless that new rewrite matches any that have previously existed...

Thank you MC and Simon for your explanations - much appreciated. I do not expect to be having to change url's too often but if a url is changed, is the new url automatically redirected to the original url? i.e. can the target continue to be accessed via the old url? I assume so but just double checking :smile:

thanks again,
Mike

shags38:

Thank you MC and Simon for your explanations - much appreciated. I do not expect to be having to change url's too often but if a url is changed, is the new url automatically redirected to the original url? i.e. can the target continue to be accessed via the old url? I assume so but just double checking :smile:

thanks again,
Mike
I say this because if not mistaken, I've seen comment about "dumping the database" and starting all over. Provided the associated ceon database tables and actually the product, ezpages, categories, manufacturers to which that points are the same as they've "always been", then... yes, a uri that previously existed will still direct to whatever the current uri is in a single redirect. I stated this a few of my posts ago specifically to try to prevent having to answer it again, though it seems I didn't say it right, sorry.

Btw, I just went through the documentation to try to help a little further. If you look at the configuration section. Scroll down a little bit and will see a list of links to the remaining content. Pick any of the four "Specifying the Current URI Mapping for" links. Then scroll a little below that where it is described how to Change the current URI... the above is described/noted about.

Zen Cart 1.5.7
PHP 7.4.12
Ceon URI Mapping 5.1.0

I had a number of warnings logged from this module.

The first is in includes/classes/class.Transliteration.php
The warnings are like, and spread across multiple locations within the file.

PHP Deprecated: Array and string offset access syntax with curly braces is deprecated in /home/xxxx/public_html/includes/classes/class.Transliteration.php on line 118.

The fix is to replace the { } with [ ]

For example, line 118 was

if ($str{0} < "\x80") {

and should be changed to

if ($str[0] < "\x80") {

This needs doing on the following line numbers: 118, 135, 143, 167, 169 (twice), 171, 172 (twice), 174, 175 (three times), 177, 178 (twice), 179 (twice).

Zen Cart 1.5.7
PHP 7.4.12
Ceon URI Mapping 5.1.0

The second file logging errors is admin/includes/classes/class.CeonURIMappingInstallOrUpgrade.php

The logged error is

PHP Deprecated: Unparenthesized `a ? b : c ? d : e` is deprecated. Use either `(a ? b : c) ? d : e` or `a ? b : (c ? d : e)` in /Users/steph/Sites/localhost/liberro/anorak1/includes/classes/class.CeonURIMappingInstallOrUpgrade.php on line 467

This error is logged on 467, 472,477, 48, 485

To fix, replace the following lines 465 to 489

$fallback_defines = array(
			'product_reviews' =>
				isset($default_uri_parts[$default_language_code]['product_reviews']) ?
				$default_uri_parts[$default_language_code]['product_reviews'] :
				isset($default_uri_parts['en']['product_reviews']) ?
				$default_uri_parts['en']['product_reviews'] : 'Reviews',
			'product_reviews_info' =>
				isset($default_uri_parts[$default_language_code]['product_reviews_info']) ?
				$default_uri_parts[$default_language_code]['product_reviews_info'] :
				isset($default_uri_parts['en']['product_reviews_info']) ?
				$default_uri_parts['en']['product_reviews_info'] : 'Review',
			'product_reviews_write' =>
				isset($default_uri_parts[$default_language_code]['product_reviews_write']) ?
				$default_uri_parts[$default_language_code]['product_reviews_write'] :
				isset($default_uri_parts['en']['product_reviews_write']) ?
				$default_uri_parts['en']['product_reviews_write'] : 'Write a Review',
			'tell_a_friend' => isset($default_uri_parts[$default_language_code]['tell_a_friend']) ?
				$default_uri_parts[$default_language_code]['tell_a_friend'] :
				isset($default_uri_parts['en']['tell_a_friend']) ?
				$default_uri_parts['en']['tell_a_friend'] : 'Tell a Friend',
			'ask_a_question' => isset($default_uri_parts[$default_language_code]['ask_a_question']) ?
				$default_uri_parts[$default_language_code]['ask_a_question'] :
				isset($default_uri_parts['en']['ask_a_question']) ?
				$default_uri_parts['en']['ask_a_question'] : 'Ask a Question'
			);

with

$fallback_defines = array(
			'product_reviews' =>
				isset($default_uri_parts[$default_language_code]['product_reviews']) ?
				$default_uri_parts[$default_language_code]['product_reviews'] :
                (isset($default_uri_parts['en']['product_reviews']) ?
				$default_uri_parts['en']['product_reviews'] : 'Reviews'),
			'product_reviews_info' =>
				isset($default_uri_parts[$default_language_code]['product_reviews_info']) ?
				$default_uri_parts[$default_language_code]['product_reviews_info'] :
                (isset($default_uri_parts['en']['product_reviews_info']) ?
				$default_uri_parts['en']['product_reviews_info'] : 'Review'),
			'product_reviews_write' =>
				isset($default_uri_parts[$default_language_code]['product_reviews_write']) ?
				$default_uri_parts[$default_language_code]['product_reviews_write'] :
                (isset($default_uri_parts['en']['product_reviews_write']) ?
				$default_uri_parts['en']['product_reviews_write'] : 'Write a Review'),
			'tell_a_friend' => isset($default_uri_parts[$default_language_code]['tell_a_friend']) ?
				$default_uri_parts[$default_language_code]['tell_a_friend'] :
                (isset($default_uri_parts['en']['tell_a_friend']) ?
				$default_uri_parts['en']['tell_a_friend'] : 'Tell a Friend'),
			'ask_a_question' => isset($default_uri_parts[$default_language_code]['ask_a_question']) ?
				$default_uri_parts[$default_language_code]['ask_a_question'] :
                (isset($default_uri_parts['en']['ask_a_question']) ?
				$default_uri_parts['en']['ask_a_question'] : 'Ask a Question')
			);