Checkout issue with W3TC Browser Caching setting

  • Resolved smashballoon

    (@smashballoon)


    6 years, 6 months ago

    Hey guys,

    We use the W3 Total Cache plugin and recently updated it to the latest version. After doing so, we noticed an issue with the EDD checkout – it displayed a 0 instead of the form used for customers to enter their personal info (screenshot). I tweaked the W3TC settings and found that this only occurs when the ‘Browser Caching’ setting is enabled. When it’s disabled the issue doesn’t occur.

    I understand that this might be a bug in W3TC, but as it’s a major plugin I figured I’d reach out to you guys first to see whether it’s a known issue that anyone else might have reported or if you’re able to replicate it at all.

    Thanks in advance for any assistance!

    John

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Contributor Pippin Williamson

    (@mordauk)

    John,

    I have not seen this reported elsewhere.

    Does the problem go away if you add /checkout to the exceptions list in the Browser Caching settings?

    Thread Starter smashballoon

    (@smashballoon)

    Hi Pippin,

    Thanks for the fast response! Adding the /checkout exception doesn’t resolve the issue, but I was able to narrow this down further by testing the individual Browser Caching settings. The issue only occurs when the following setting is enabled:

    Remove query strings from static resources
    Resources with a “?” in the URL are not cached by some proxy caching servers.

    When that setting is disabled then the problem goes away, but when it’s enabled it occurs again.

    We’ll just keep that setting disabled for now – not a big deal – but wanted to pass the information on.

    John

    Plugin Contributor Pippin Williamson

    (@mordauk)

    That’s a weird one for sure. . . my guess is that the option is somehow modifying the ajax processing URL that EDD uses. Why it’s doing that, I really can’t say, sorry.

    Thread Starter smashballoon

    (@smashballoon)

    No probs, we’re fine just keeping that setting disabled. I did run another quick test though and compared the admin-ajax request when that setting is enabled and disabled. It looks like the issue is that the nonce is being stripped from the form data. This is when the setting is disabled: action=edd_load_gateway&edd_payment_mode=paypal&nonce=4cf0ee8bad and when it’s enabled: action=edd_load_gateway&edd_payment_mode=paypal. I’m not sure why it’s happening exactly but thought I’d pass it along.

    Thanks for the quick support!

    John

    Plugin Contributor Pippin Williamson

    (@mordauk)

    That looks to be a bug in that setting for sure. Nonces shouldn’t ever be stripped away.

    The purpose of that particular setting is to remove query strings from assets (images, CSS files, JS files, etc). In this case it’s removing the query string from an API URL endpoint.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Checkout issue with W3TC Browser Caching setting’ is closed to new replies.