by
KK » Thu Mar 12, 2015 5:04 am
Thanks for the access creds.
I had a look and found that the problem was not specific to Safari alone - it'd appear in any browser that did not have you logged-in as admin.
The reason (as is often the case when things are fine for admin but go awry for normal users) was caching.
The form would contain a security token from the time the page was last cached and this would not tally with the one generated for the current submission. Admins are never served cached contents so this problem doesn't appear when you are logged-in as one.
To rectify the problem, save some changes in the admin-panel to destroy the current cache and then put a <cms:no_cache /> tag in the template carrying the form to prevent it from being cached again.
Hope it helps.