[wp-trac] [WordPress Trac] #24447: Avoid losing data after nonces expire
WordPress Trac
noreply at wordpress.org
Thu Jul 30 05:18:06 UTC 2015
#24447: Avoid losing data after nonces expire
-------------------------------+-----------------------------
Reporter: azaozz | Owner: iseulde
Type: defect (bug) | Status: assigned
Priority: normal | Milestone: Future Release
Component: Administration | Version:
Severity: normal | Resolution:
Keywords: needs-patch early | Focuses:
-------------------------------+-----------------------------
Comment (by majick):
Outputting the raw post content may not be a good user experience but
neither is the current "Are you sure you want to do this?" screen, which
is just unhelpful and out-dated. I agree returning the user to the post
writing screen and letting them know the post has not been saved would be
better than this, but the locally saved data may still not be as current
as the submitted data.
To avoid end user confusion and panic, another alternative solution would
be to send the user to a post revisions screen which shows the saved
content next to the newly posted content for comparison, inform the user
explicitly that their last update was NOT saved, and give the option to
update the post with the newly posted data or discard it. Probably easier
said than done, but certainly closer to ideal in preventing data loss. I
guess my point is, if nothing is actually done with the posted data,
something could still be lost when there really is no reason for that to
happen.
I realize this ticket is really about nonces and how they could be
improved in this case, this alternative could be split off as a new
ticket for discussion if it's getting too off-topic. I will leave the
nonce side of things as I admit I'm not familiar enough with them to
really contribute much on that front.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/24447#comment:27>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list