Ceon URI Mapping v4.x

[lhungil]

... If you didn't want to answer, you shouldn't have. ... I know there are a lot of people like you on here, dedicating time free of charge to help. ...

If "we" did not want to help, we'd just not respond... But anyhow we are getting off track. Basically, the behavior you are seeing is not something we can replicate in our test environments (working copy of Zen Cart with a functioning template and CEON URI Mapping)...

So the question becomes "What is different on your installation?". Right now we do not know (possibly because you do not know exactly what is different in your installation from a stock Zen Cart 1.5 installation)...

... Other links, such as the header and footer links are hard coded into template. ...

All links should be using zen_href_link to "populate" the HTML "href" attribute (dynamic not hard coded). This holds true for templates, modules, plugins, and anything else inside Zen Cart's installation folder. I cannot stress this enough!

... Debug log: There are some, which I'm trying to work my way through. I don't think any are connected to this, but i'll double check. ...

Usually when these are created something is wrong... Sometimes seemingly unrelated errors can be the root cause... I usually advise clients to start by cleaning up all existing errors (especially after an upgrade)... If you posted some snippets (please use the # code blocks), we may be able to help (although if you feel they are unrelated, feel free to search for a more appropriate thread or start a new one)...

... In terms of the installation, the hosting company updated ZC to the latest version, and updated the CEON plugin around the same time. My hunch is that something hasn't been installed properly ...

Ahhh, so it was not a clean Zen Cart 1.5 installation, but an upgrade from a previous version... I would be asking the hosting company HOW they upgraded the installation... Did they try to use fantastico, scriptalicous, etc (which can cause some serious headaches on customized sites)? Did they just attempt to merge changes from 1.5 into 1.3 files? Did they follow the steps outlined on this site by the Zen Cart team for doing an upgrade? In what ways did they deviate (if any)? Did they restart from scratch (does not sound like it)?

I'd say your hunch is correct... Something was broken during the upgrade of Zen Cart, another module, or this module...

... We have customised some quite a bit of functionality on the site, but most of that customisation was done around initial build. ...

Zen Cart 1.3 and 1.5 have significant differences. One example is changes to the handling of admin menus / pages (plugins need to be upgraded to work correctly).

When upgrading, many of us recommend only doing an upgrade of the database and configure.php files... And starting with clean files from Zen Cart 1.5 and slowly re-adding any needed customizations to the Zen Cart files...

This avoids bad "merges" and makes it easier to determine "when and what" went wrong during the upgrade... Another reason is some older plugins and modifications are no longer needed with Zen Cart 1.5 (and leftover files / merged code can cause issues)...

... Unfortunately we had help with the update, and as such I'm not 100% sure where it's gone wrong, barring uninstalling and reinstalling. ...

Crux of the issue here... It sounds like you are not aware of exactly what was done...

Walking thought the installation steps (for this module) again should help verify where something is off (have you done this?)... As will going though the debug logs... One can also compare their current site against a clean 1.5 installation to see what changes have been made...

But in the end if whoever upgraded your Zen Cart installation and plugins made a mistake (and was paid)... I'd be giving them a call... Otherwise, manually starting over the upgrade and installation (on a development site) may be a safe last resort...