Issue Resolved! Thanks to our dedicated webmaster, we resolved this issue. Posting here in case anyone else encounters the same challenge: Our admins had trouble finding the issue because they were logged into our WordPress account when testing. The form worked as expected. However, when logged out of WordPress completely (and using an incognito browser window – just in case), they were able to duplicate the issue.
Here’s what we figured out:
SiteGround’s server-side caching works differently for logged-in WordPress admins. Admins bypass the cache entirely, so they always see fresh, dynamic content. Logged-out visitors, however, were being served cached versions of the form pages. This is why the form worked correctly when signed into WordPress.
To fix the issue, we corrected the URL exclusions in SiteGround’s caching settings to ensure that section of the site always displays a fresh, individual session regardless of whether the user is logged in.
