• Resolved mattsteinruck

    (@mattsteinruck)



    We’ve routinely gotten feedback from customers using our Membership form with this note:

    “Good Afternoon,
    After I ordered… I received this message….

    “You are missing the payment key to view this donation receipt.”

    What does this mean? Will I be receiving the quarterly books I ordered?
    Thanks!”

    I’ve seen a couple posts about this message suggesting caching issues and other site edits, but I’m clear yet on what I need to adjust to diagnose or change this. It’s been an issue for about a year. Can you suggest a step-by-step of how we can finally fix it?

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Matt Cromwell

    (@webdevmattcrom)

    Hi @mattsteinruck — thanks for reaching out about this and for being a Give user for a year already!

    You are right that that issue is most likely caching related. In order to provide a step-by-step of what you need we’d need to know abit more about your environment. Specifically:

    1) Who is your webhost and do they provide any server-side caching of your site directly or via their own custom plugin. A good example of this is Siteground who has server caching with a plugin called the SG Optimizer. Another example is WPEngine, who provides server-side caching but no custom plugin.

    2) Additionally, do you have any caching plugins that you are using, like W3TC or Super Cache or WP Rocket? If so, each of those provide ways to prevent their caching from being applied to the Donation Confirmation page.

    3) Lastly, we took some extra steps in Give 2.2 to help prevent this problem generally speaking. The Donation Confirmation table now loads over AJAX which prevents caching plugins from caching the information. Are you updated to the latest version of Give? If so, have you still gotten feedback about this issue since that update?

    Let me know on those items and we’ll do our best to guide you the rest of the way from there.

    Thanks!

    mattsteinruck

    (@mattsteinruck)

    Thanks Matt.

    The site is in WPEngine. Is there something I’d need to do on their end from a cache-setting standpoint?

    One of the biggest things is that – no. We haven’t updated our version of GIVE. I’ve been hesitant to do so, not sure if/what other things it may impact adversely within their existing processes. But if it’s pretty safe to do, and only will make things better, than that’d be my first step, I assume.

    Is there protocol/precaution needed to press GO on that update process?

    Plugin Support Ben Meredith

    (@benmeredithgmailcom)

    WP Engine has a great solution for testing updates, by spinning up a new staging site to make sure that things go smoothly. That would be our first recommendation. See their documentation here on that: https://wpengine.com/resources/what-is-a-staging-site-why-have-one/

    If you run into issues once you do that, let us know.

    Also, this is a known issue with WPEngine’s caching on older versions of Give. See this article for a fix:

    ​https://givewp.com/documentation/resources/wp-engine-cache-exclusion-donation-confirmation-page/

    The new method is the most recent versions of Give makes this issue a bit more cache-agnostic, and should resolve things, too.

    ​​Let me know if that resolves things, or if you need further assistance. ​Thanks for using Give! Have a great day.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.