Cached Fundraising Page Issues

Use this guide when logged-out visitors see stale fundraising amounts, donation counts, suggested amounts, custom amount settings, or campaign open/closed status.

Overview

Use this guide when logged-out visitors see stale fundraising amounts, donation counts, suggested amounts, custom amount settings, or campaign open/closed status.

Symptoms

  • Admin sees correct campaign data.
  • Logged-out visitors see old values.
  • Purging page cache temporarily fixes the problem.
  • Donation controls do not match current plan settings.
  • Campaign appears closed when it should be open.

Likely Causes

  • Cached HTML is stale.
  • REST hydration is blocked.
  • JavaScript failed.
  • CDN or security plugin cached the campaign state endpoint.
  • Donation launcher or no-JavaScript route is cached incorrectly.

Resolution Steps

  1. Test as a logged-out visitor in a private window.
  2. Confirm campaign REST hydration requests are not blocked.
  3. Clear page cache and CDN cache.
  4. Exclude launcher, webhook, success, and no-JavaScript donation routes from cache.
  5. Confirm JavaScript is running on the page.
  6. Complete a new test donation and watch metrics update.

Expected Result

The public page may load from cache, but metrics and controls should hydrate with current campaign state.

Additional Notes

PayPress is designed to keep donation and fundraising pages cacheable while loading current state separately. Checkout validation still happens on the server.

Related Articles