Description of the need
When .htaccess, robots.txt, or settings.php have been updated in a release, we should update them when safe/possible
Proposed solution
We could store a hash of the previous version of the file in state. When doing an update, check the hash in state to see if the contents of the file has been changed. If not, we can overwrite it (assuming Backdrop has permissions to write to files outside of core) and update the hash with the hash of the new file.
Alternatives that have been considered
- https://github.com/backdrop/backdrop-issues/issues/5911 (but I think we should do both)
Draft of feature description for Press Release (1 paragraph at most)
Backdrop core can now automatically update files outside the core directory -- assuming they have not been previously modified and that Backdrop has permission to write to those files.
Recent comments
Another contrib module came to my mind: Save & Edit. Of course, that's also not what you had in mind - it saves to the server. But it can be helpful when the network the author's...
Implementing autosave in Ckeditor 5
... Autosave module that you mentioned, but it saves to the database I thought, that's what you're after. I am looking for is to save to localStorage...
Implementing autosave in Ckeditor 5
Thanks for your prompt reply. I tried the Autosave module that you mentioned, but it saves to the database, and the behavior I am looking for is to save to localStorage, in other words,...
Implementing autosave in Ckeditor 5