Public Manifyst events work with page caches—WP Rocket, W3 Total Cache, LiteSpeed Cache,
and host-level caches—without exclusions or special settings.
Public event pages are built to be cache-safe for visitors who are not logged in: the page
markup is identical for every anonymous visitor, and signups do not depend on anything that
could go stale inside a cached copy. A cached public event page keeps accepting signups for
as long as your cache keeps it.
Two things are worth knowing:
Availability counts can lag on a cached page. The "3 spots available" numbers are baked
into the cached copy, so they reflect the moment the page was cached. The live check still
happens at signup time — if a slot filled since the page was cached, the visitor is offered
the waitlist or told the slot is full rather than being overbooked. Signing up also refreshes
the numbers on the page in place.
No exclusions are needed for a public signup form. Some plugins recommend excluding all
their pages from caching; Manifyst does not.
Password-protected events are different. Their locked and unlocked pages vary according
to WordPress's password cookie. Manifyst therefore marks both states as non-cacheable using
WordPress no-cache headers and the standard page-cache opt-out. The same protection applies
when a password event is embedded with the Manifyst Event block or [manifyst_event].
If signups fail only for logged-out visitors, or a password form keeps returning after the
correct password, clear that page from the cache once. If the problem returns, ask the host
whether its edge cache respects Cache-Control: no-cache, must-revalidate, max-age=0.
