Hi all! I've got a bit of problem that I think may be related to caching but was hoping for confirmation or a workaround from the community.

Mid-January our hosting provided move to Pantheon.io. They have a Page Cache Max Age setting of 1 week for the lowest setting I can adjust to in WordPress. Ever since the migration, I have had a nightmare of my scheduled Formidable Forms not displaying their custom closed messages when they close or showing the form properly when a form re-opens. I always have to manually clear the forms' page cache for things to work.

Now, I've just noticed that the default [date] option for a date field in a form can be as far off as 3 or 4 days from the created date for the form. Looking through past entries, this disparity of dates has coincided with the Pantheon migration.

I know that people aren't opening this form and leaving it open their browser for 3-4 days before submitting it. I've verified this directly with 3 of the people that I trust their memory that had these date gaps. Plus, these aren't big forms. It's a certificate form so we only ask for their name and email. The date field is actually hidden from all but the administrator, and it's marked Read Only.

Is there something I can do to make sure the [date] field is always pulling a fresh date field regardless if the person is getting a cached version of the page? Is this a Formidable problem or a Pantheon problem?

Is there a workaround someone might suggest? I thought about allowing them to pick their own date, but I don't want to allow them to pick any date in the future other than the current date with a picker.

Any guidance would be super helpful and appreciated.