Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • I am very grateful for this suggestion of plugin conflict testing. I did as you suggested: I enabled maintenance mode and disabled all the plugins except for WooCommerce, and the issue did not still happen. So I then re-enabled plugins one-by-one and discovered that enabling the WPML String Translation plugin causes the issue to happen again. We do use that plugin for driving a currency selector in our shopping cart interface, though, so I’m not quite sure how to proceed at this point. But it’s very good to have more insight into where the conflict may be!

    I appreciate your continued suggestions and guidance! I have updated the URL settings to include the https, and the guest checkout problem persists. You can see the updated system status report here: <https://privatebin.net/?0391608ed4ffd79c#3TTYpFePPJ3Q6o8iK7fyZKFVaANdgwPdr6wTXYh48qx8>.

    We are using Cloudflare, and I have activated development mode, but it hasn’t affected the guest checkout problem, so it doesn’t seem like Cloudflare caching is affecting the situation. We do have full SSL mode enabled; I’m not sure how to see if there is any URL bouncing between http and https schemes or between www and non-www domain names (but I don’t think that is happening). I’m still happy to send you details of our Cloudflare configuration, if you think that’s useful.

    I’m going to start looking into server-level caching.

    Thanks very much for your detailed response! There are several threads that I want to pursue based on what you wrote, but I only have a limited time at the moment, so I’ll start with the system report that you requested, and come back for some additional follow up. Here’s a link to a paste of the system report: <https://privatebin.net/?e997df6997d4ecfd#35oteMiW1kmFbBByKKVQc6bv7LZ74kmQqK3tL8WWwsmW>.

    As we’ve been investigating the cookie situation on both staging and production, I see the woocommerce_cart_hash cookie on staging (using the browser dev console), but not on live, so I do agree that it is likely a session or caching issue, but it’s been very hard to identify where the caching may be happening. Also, I haven’t seen the wp_woocommerce_session_ cookie on either staging or production; instead, I see a cookie named wp_woocommerce_session_hash, where hash is a hash value.

    I will share more about what is happening with our caching systems soon (perhaps later today or tomorrow).

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