CSRF token error improvements

[robdekort]

Every now and then I get an email from a client with a screenshot showing the CSRF token error in the CP. This error means nothing to them and they usually think they did something wrong.

It would be helpful to explain to the user what the error is, why it happened and how it can be prevented.

Alternatively, to prevent data loss (this unfortunately happens), perhaps the token could be automatically polled?

[jasonvarga]

Could we see the screenshot? And it would be helpful to see the URL when they get the error.

perhaps the token could be automatically polled?

We do have the session expiration component already, which should be handling that. If it isn't, I guess that's a bug.

[robdekort]

It's not a great pic, sorry about that, but this is the one I got last:

The URL in this case was: /cp/collections/pages/entries/home

I assumed they were editing and went for lunch, which triggered the error. Not sure about that however.

[jasonvarga]

That's good, thanks. The session expiry popup should've happened, but:

• it didn't somehow
• they dismissed it
• they dismissed it accidentally

[robdekort]

Gotcha. That might very well have happened. I didn’t know this was even in there. That’s great. Perhaps then my suggestion is just improving this error message?

[jasonvarga]

Yeah, or if they were able to dismiss the dialog we should prevent that. Maybe just prevent clicking the overlay or hitting escape from closing it. People might have a legit reason to close it so we should just remove the accidentalness of it.

[robdekort]

Right yeah!