Add to Cart Issue

  • Resolved Darryl.R

    (@darrylr)


    5 years, 1 month ago

    Hi, thanks for a great plugin!

    I have a issue with the 3.7.1 update.

    I suspect it may have to do with caching, but I’m not sure; as my site has the below string appended to the domain

    https://www.mydomain.co.za/?v=68caa8201064

    So, when I click add to cart in the product list pages; the page starts loading and the URL presents as the following:

    https://www.mydomain.co.za/?add-to-cart=218?v=68caa8201064

    The item does not get added to cart, but the page reloads on its own immediately and settles on the below URL, adding the bold bit;

    https://www.mydomain.co.za/?add-to-cart=218?%3Fv%3D68caa8201064&v=68caa8201064

    It seems this bit %3Fv%3D68caa8201064& is an added and escaped version of this ?v=68caa8201064

    I did disable all my plugins except Woocommerce and the issue persists. I have the same theme running on my staging site, and that’s working fine.

    When I roll back to 3.7.0 the issue disappears.

    Any help would be appreciated! Thank you

    • This topic was modified 5 years, 1 month ago by Darryl.R. Reason: clarity, typo's
    • This topic was modified 5 years, 1 month ago by Darryl.R. Reason: clarity, typo's
Viewing 6 replies - 1 through 6 (of 6 total)
  • mother.of.code

    (@imazed)

    The Mother of Code

    Hey there!

    Can you start by copy and pasting the system report for this site? You can find it under WP Admin > WooCommerce > Status > Get system report > Copy for support. That will provide us with a bit more information to go on.

    I agree that it looks very much like a caching issue. Have you also asked your hosting company whether they are applying any caching services?

    Thread Starter Darryl.R

    (@darrylr)

    Actually, I’ve just figured it out. Its the caching string that Woocommerce adds to the URL when you use the Geolocate (with page caching support) option under Woocommerce –> Settings –> General.

    When I change it to Geolocate, the problem is solved; but obviously there is still an issue if you want to use Geolocate with page caching support.

    dougaitken

    (@dougaitken)

    Automattic Happiness Engineer

    Hey there @darrylr

    I did disable all my plugins except Woocommerce and the issue persists. I have the same theme running on my staging site, and that’s working fine.

    To confirm what you’re saying here, you have 3.7.1 on a staging site and it is working without a problem but with the exact same setup, your live site is presenting this error?

    If the only difference between working and not working with 3.7.1 is your server setup then I feel this is pointing towards some server level caching or something which isn’t the same on the live environment compared to the staging.

    Thanks,

    Thread Starter Darryl.R

    (@darrylr)

    Hey @dougaitken

    To confirm what you’re saying here, you have 3.7.1 on a staging site and it is working without a problem but with the exact same setup, your live site is presenting this error?

    Both sites are on the same server, the staging site is a live staging site.

    If the only difference between working and not working with 3.7.1 is your server setup then I feel this is pointing towards some server level caching or something which isn’t the same on the live environment compared to the staging.

    Its definitely the Geolocation caching. So I solved my immediate issue when I changed the setting to Geolocate, but i’m guessing those that want to specifically use Geolocation catching may still have a problem.

    dougaitken

    (@dougaitken)

    Automattic Happiness Engineer

    Hey @darrylr

    Thanks for the reply here!

    Both sites are on the same server, the staging site is a live staging site.
    but i’m guessing those that want to specifically use Geolocation catching may still have a problem.

    To me, this is pointing to a server-level caching difference between the live and staging.

    I’d ask your host if they have any advice for you on this one.

    As it is not specifically related to the function of WooCommerce but is server/caching related, I will mark this thread as Resolved for now, but please do open a new one if you need any more help!

    Thanks,

    Thread Starter Darryl.R

    (@darrylr)

    Hi @dougaitken

    To me, this is pointing to a server-level caching difference between the live and staging.

    Its the same server, same settings, etc?

    As it is not specifically related to the function of WooCommerce but is server/caching related, I will mark this thread as Resolved for now, but please do open a new one if you need any more help!

    It has to do with the Geolocation (With Caching) setting in Woocommerce. Please confirm if this setting has to do with/makes use of server-side caching? i.e. are you saying that server-side caching and Geolocation (with caching) is the same thing?

    Other than that you can close this thread, I solved the issue by setting it to Geolocate without caching

    Thanks

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Add to Cart Issue’ is closed to new replies.