token expiration means data loss and effort wasted
LQ Suggestions & FeedbackDo you have a suggestion for this site or an idea that will make the site better? This forum is for you.
PLEASE READ THIS FORUM - Information and status updates will also be posted here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
token expiration means data loss and effort wasted
Can the system be fixed so that all the input prior to clicking preview post isn't discarded after learning the token has expired? I can't recall encountering this kind of disrespect for interrupted effort in other forums. I just lost another half hour's work with a mouse click.
I thought I was the slowest typist in the world ...
Haven't had that, but going back in the browser does similar - I highlight and <ctrl>-C these days ... :shrug:
There was talk of a "save as draft" facility a while back, but that seems to have gone cold. A fix would be nice.
"prior to clicking anywhere" the text you typed does not exist anywhere, but in a local buffer. Depends on the browser you use.
Clicking on anything which will drop the editor window may have such outcome (= the text is lost).
Actually I started to write a post yesterday and continued today, after a reboot. The entered text was still there....
Right after ondoho's reply I installed extension textarea cache. Moments ago I was composing a Quick Reply here and accidentally opened a bookmark on top of it. On back, textarea was empty. I had left this thread in an open tab, composed a reply, tried Go Advanced, and was greeted with logged in since, press back, and an empty textarea on back.
^ Sorry to hear that.
Textarea cache is needlessly complicated (the saved text is difficult to find), but it has always saved me in the end.
You can also adjust the frequency how often it saves the textarea's content.
This remains a recurring frustration, often causing me to close the tab and forget I even tried. It even happens when I think to reload the page prior to beginning a response, making second try expirations, which is pretty much the routine when I do retry, even more egregious.
Too much time and effort gets lost. Why does the token even have an expiration anyway?
Which browser?
I still use Textarea Cache, but I find that Firefox kind of has this functionality built in nowadays - most of the time I don't need the addon.
And personally I don't think it's LQ's fault - it's simply how web pages work. I have had this problem on other sites too.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.