|
Adam Beecher
|
July 31, 2013 at 7:43 am
There are a couple of threads about the Back button causing data from the current session to be overwritten, however a client of mine is seeing completely unrelated data go missing. Specifically, a payment from July 17 doesn’t have a corresponding record in EE, and when my client went to test the system himself on the 26th (when the issue was reported), his own test record AND the record of the person before his test record were deleted. There was absolutely no session relationship between the test record and the previous user.
This webserver is behind a Varnish cache, but unless EE is using some kind of non-standard session management, that shouldn’t be an issue. I’ve since upgraded EE to current (although that shouldn’t have been the problem, since the previous bug was remarked as having been related to sessions) and set the relevant URLs to pass through Varnish, but there are thousands of registrations to go through this system and my client is seriously concerned about data loss.
I’d like someone from EE to review the system please. This kind of data loss is very troubling.
|
|
Josh
|
July 31, 2013 at 8:34 am
Hi Adam,
Can you clarify when they did the test whether or not they hit the back button? If you were to test this out now with the new version installed you’ll find that there’s a warning message that pops up warning the customer to not click the back button. This was added in the recent update of Event Espresso to help eliminate this issue.
The warning message will instruct the customer that if they click the back button it will overwrite their current registration (because the session has not been cleared yet).
|
|
Adam Beecher
|
July 31, 2013 at 8:36 am
Hi Josh,
They did hit the back button, however please refer to my initial message after the word AND.
Adam
|
|
Josh
|
July 31, 2013 at 9:13 am
This is what I’m referring to:
AND the record of the person before his test record were deleted. There was absolutely no session relationship between the test record and the previous user.
This isn’t something we’ve been able to reproduced in testing. However it may be related to the Varnish caching.
This webserver is behind a Varnish cache, but unless EE is using some kind of non-standard session management, that shouldn’t be an issue.
It shouldn’t be an issue, but it sounds like you’ve taken some steps to reduce the likelihood of this happening by setting the URLs that handle the registration process to pass through Varnish. We generally recommend not caching the pages that handle the registration process.
|
