Autosave a shadow copy (local storage perhaps) of an ongoing edited file to prevent data loss in case of session timeout
My suggestion lies on the fact that I indeed lost my work on a php file that was open in the code editor, when I absent-mindedly pushed the "Apply" button on the text editor and realized with horror that my admin session timed out and I was returned to the unmodified version of the file once logged back in.
It would be convenient to autosave in the background ongoing changes of a text file that is bound to change once opened in the editor, in order to prevent data loss.
Αθανάσιος Κόντης (CodeVortex)
shared this idea
-
Larry
commented
Normally one would push to a plesk git repo or upload files. I was not able to set up git and instead was editing a file directly in Plesk code editor. After writing for a while I was satisfied and clicked "Apply". Unfortunately I got logged out as soon as I did. When I logged in my changes were all gone.
If there was a warning that I will get logged off and will lose changes or an autosave that remembers my changes that would save other users in my position from frustration.