Getting ajax error in v155 with v154 Westminster template

Okay since upgrading to 155 I am having an issue with clicking on the LOGIN option, when I click it I am getting this come up ..
Attachment 16134

This is happening on a site I have upgraded from 154 to 155 and it is also happening on a new site running 155. However a site running 154 with the same theme works fine??

The site that's working okay on 154 is .. http://www.testmcs.mikes-cs.co.uk/

The site that has the issue is .. http://www.suessweets.co.uk/

I know those 2 links are running different themes but even if I use the same theme the error is still there.

Any advice but be appreciated as I have no idea where to look. Many thanks in advance.

That's an error during an ajax call ... which suggests that the ajax-related files (/ajax.php, /includes/classes/ajax/*, and /includes/templates/your_template/jscript/jscript_framework.php) are damaged or altered from what comes with v155 out-of-the-box.

Can you confirm WITH ABSOLUTE CERTAINTY that it has nothing to do with the new templates you've been adding?

I previously had an error with ajax.php because the subversion script I had to update for changes didn't update the files in the root directory.

Check that your /ajax.php file has been properly updated.

The suessweets website was a clean install of 155 and a clean install of the theme, the other website in my post is running 154. My own website gets the same error when using the same theme however if I change the theme back to Bask Black the login link works.

I have also attempted to replace the ajax.php file from the Zencart 155 zip

DRBYTE taking your comments I changed the Sues Sweets theme to the default responsive theme that comes with 155 and it worked, swapped it back to Winchester Blue and the error comes back ???

It seems weird that I`m using the same files uploaded to 2 sites, the one on 154 works fine the one on 155 errors ??

As I said earlier, the Westminster template replaces some core v155 files with older versions.
Two of note are:
/includes/templates/YOUR_TEMPLATE_FOLDER/jscript/jscript_framework.php
/includes/classes/Mobile_Detect.php

And maybe others. Copy the v155 versions of those files back in, and see what happens.

Quote:

---

Originally Posted by DrByte

As I said earlier, the Westminster template replaces some core v155 files with older versions.
Two of note are:
/includes/templates/YOUR_TEMPLATE_FOLDER/jscript/jscript_framework.php
/includes/classes/Mobile_Detect.php

And maybe others. Copy the v155 versions of those files back in, and see what happens.

---

I have replaced the mobile_detect.php as advised but I`m unsure what you want me to do about the Jscript_framework, you say that the Westminster replaces the core files but the file you specify is in the Westminster folder anyway ??

Quote:

---

Originally Posted by MCS_Computers

I have replaced the mobile_detect.php as advised but I`m unsure what you want me to do about the Jscript_framework, you say that the Westminster replaces the core files but the file you specify is in the Westminster folder anyway ??

---

Yes, and in the code following loading sequence, the template's version of the file (especially if called the same filename) is loaded in place/ahead of the same file in the template_default equivalent location. Therefore it "replaces" the default version of the file... So either physically replace the file in YOUR_TEMPLATE directory structure or remove it from there, I would suggest replacing instead but I haven't looked at the two sets of code to identify if there is anything that needs to be merged between the two.

Okay I have looked in the clean 155 folder and this file is in there twice in the jscript folder of the themes, therefore I`m not sure how uploading the Westminster theme had replaced these files however I have replaced this file in the themes folders as specified and also uploaded the Westminsters version back to the Westminster folder and it is still the same.

It doesn't "replace" them in the strictest sense of the word. The code in the new template overrides them, so that their code is not executed, which is the same effect if they had "replaced" the core files. So being they are overriding core you need to take the core files and use them to actually replace the same files in the new template.