• Resolved dav74

    (@dav74)


    Hello,

    We had an ajax issue on the secondary language pages of our shop on our website. The “add to cart” ajax calls from the category pages were not working. The loading spinner would keep spinning after your tried to add a product to your cart, until it created a 503 server error (only category pages and quick view were affected). We knew it was not theme related, as we switched themes to a WP theme and the problem was still there.

    Today I uploaded an older copy of our site (with WC 5.2.1) to a staging area, and all worked perfectly. I then updated each plugin one by one. Everything worked correctly until I updated WC from 5.2.1 to 5.2.2. We then had the same ajax problem on our secondary language pages (using WPML).

    I tried to rollback WC to 5.2.1 but then all shop pages just had 500 internal errors.

    Can you please advise how we proceed? This is a bug with WC 5.2.2 and I presume WPML.

    • This topic was modified 5 years, 1 month ago by dav74.
Viewing 4 replies - 1 through 4 (of 4 total)
  • hi, I also have the same problem

    laceyrod

    (@laceyrod)

    Automattic Happiness Engineer

    Hi there,

    Thanks for reaching out and reporting this issue.

    As we didn’t develop WPML ourselves, you’ll want to reach out to their team directly to let them know that it isn’t compatible with the most recent version of WooCommerce. It’s likely they may already be aware of the issue and have a fix in progress or a workaround.

    Thanks for your understanding!

    Thread Starter dav74

    (@dav74)

    Hello,

    Thanks for your reply. What is very strange is that we took a copy of the live website which has this ajax problem on the secondary language pages, and put it on to a new staging URL (a different TLD). We checked the site and the problem was gone.

    How can this be? Any ideas? As I said, 2 identical sites. On one URL it works without issue and on the other not.

    Plugin Support Aashik P – a11n

    (@aashik)

    Hi there!

    How can this be? Any ideas? As I said, 2 identical sites. On one URL it works without issue and on the other not.

    As @laceyrod pointed out, the best source of support, in this case, would be WPML developers and we did not develop the extension ourselves and are not aware of existing bugs/workarounds.

    I’ll mark this topic as solved for now. Please feel free to open a new topic if you have any other questions specific to core WooCommerce queries.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Bug with latest release and WPML’ is closed to new replies.