It sounds like you haven't restored /admin/product.php to its original Zen Cart 1.5.6a version.
Printable View
It sounds like you haven't restored /admin/product.php to its original Zen Cart 1.5.6a version.
I copied the barebones admin back on top and it worked.... so appears issue is with USU file change???
I am going to start again with a fresh clean directory and only load USU and repost what I find. Thank you!
Will this version be fixed for updating from older versions?
Thank you!
v3.0.0 identifies in its readme how to perform that update, weeding out the code fragments that were previously introduced by its now-defunct auto-installer. I'll add a couple of checks to the v3.0.0 update processing to look for (and message to the updating admin) any remnants of that previous processing that still remain.
Hello, Please remember that I started with a fresh install script.... this is what I do each time I upgrade my website.
Just an FYI
I created a new clean fresh install..... connected it with the pre-converted production database.... and moved the code over for usu-3.0.0
It showed that it updated from 2.1.16 to 2.1.17 and everything looked successful.... but it is doing the same thing.... it is not allowing me to update a product.... it just shows the name of the product in the preview and does not load the rest of the page. So, something is not working right with either the code or with older converted databases with the USU. This is the only change I have made to the standard install.
[22-Feb-2019 21:17:53 UTC] PHP Fatal error: Call to a member function format() on null in /home/com/public_html/site/admin/includes/modules/product/preview_info.php on line 65
[22-Feb-2019 21:17:53 UTC] Request URI: /admin/product.php?cPath=10214&pID=1075&action=new_product_preview, IP address: xx.xx.xx.xx
--> PHP Fatal error: Call to a member function format() on null in /home/com/public_html/site/admin/includes/modules/product/preview_info.php on line 65.
Hi Cindy, many thanks for that explanation and for the time and effort you have put into this issue. I am often slow on the uptake so just checking that I have got this right :smile:
I appreciate it being a best guess given your inheritance of the plugin! .... and I do not see it as a plugin issue anyway.Quote:
My best guess is that the canonical link handling in USU was introduced to support Zen Cart versions prior to 1.3.9 (where the built-in canonical-link handling was introduced) and was never removed.
Here is how I see it. USU worked like a charm in v1.5.1 with the /includes/init_includes/overrides/init_canonical.php included the file package and SitemapXML files were generated correctly using USU generated url's.
USU v2 does work in v1.5.5f in that it does create the user friendly URL's as it is designed to - the problem is that those URL's are not generated in the SitemapXML files - given that USU and SitemapXML versions were the same (as used in v1.5.1, and still valid) at the time of upgrade to v1.5.5f, it appears something is not correlating between ZC core files in v1.5.5f and USU and SitemapXML - given that USU is generating the files correctly then it appears something is not telling SitemapXML to produce USU generated URLs in its files. The only change in the process is changes to ZC core files in v1.5.5f - so what changed in the core of v1.5.5f to create this 'imbalance' ? If that change could be isolated it may (should) solve the issue :smile: - I really do not want to upgrade to v1.5.6 any time soon (still recovering from 155f upgrades).
I have converted all my v1.5.5f sites to CEON URI Mapping so to test your theory of removing /includes/init_includes/overrides/init_canonical.php from USU v2 I will need to look at how I can do that without creating chaos :smile:
I haven't checked it out but maybe I can have both plugins installed without creating conflict and switch between them - in your opinion is that likely to be possible?
cheers and thanks for your continuing help,
Mike
Hello lat9,
I see the issue. I had redownloaded the "beta3" from get the latest and greatest and it is now giving the 2.1.7 code instead of the beta code. Fortunately, I had deleted the actually beta3 code and was able to retrieve it and I will do some testing today and let you know how it goes.
Shrimp-Gumbo-mmmhhh