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
It's your best assistant, but don't trust it blindly test everything thoroughly. I think it's also the best teacher if you want to learn programming.
Thoughts on AI generated code contrib?
Hi Nombre Apellido We do hosting in the UK and look after a Spanish domain...If no one closer can help, please don't hesitate to reach out. The site I'm creating is for a...
innodus (Barcelona) listing – website looks compromised or no longer theirs?
This is Robert's Backdrop profile: https://backdropcms.org/account/robertgarrigos You can see he is very active in Backdrop and very experienced. And this is his company...
innodus (Barcelona) listing – website looks compromised or no longer theirs?