Hi!
Issues like these are normally caused by caching. I’m not familiar with Pantheon but I’m guessing they have some caching solution built into their platform. I would recommend adding a cache exception for the pages with forms or for the cookie set by AF, called af_submission.
Hi @fabianlindfors! Thanks for this suggestion:
Is this something new to the latest release? I have version 1.6.5 running perfectly fine on the Pantheon environment- it’s only when upgrading that there is an issue.
When reverting back to 1.6.5, I don’t see the cookie you mentioned even though I do see the success message itself. Should I be seeing it in the list of cookies?
At any rate, I have the same level of caching on both 1.6.5 as I do on the newest version. Despite clearing the cache manually through Pantheon, the newest version of AF does not have a success message. I’ll continue to mess with Pantheon’s settings, but if you have any other ideas please let me know!
There was a significant change in how submissions are handled. Instead of using PHP sessions we now use a short-lived cookie. Using a PHP session is bad as it interferes with caching across the site, making it close to useless.
The problem could be that Pantheon is able to detect a PHP session and disable caching (most caching solutions do this). They probably can’t detect the AF cookie by default though, which is why either an exclusion rule needs to be added for the form page or the form cookie.
I’m not sure clearing the cache will work as it will be filled again when you visit the form page. After submission the page will be loaded from cache again which doesn’t have the success message.
