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
Of course. I simply give my impressions of a site builder. On one side, I found that BackdropCMS and Drupal have a great system to create a site, where it is possible to customize the...
Block title combo and 2/3 things
It's great that everyone has a choice. I'm currently making a website where the H1 title is located at the top of the page in full width with a background image, 50vh height, how do you like...
Block title combo and 2/3 things
In the end, I use my <h1> with my custom layout just before the region for the content and i make a preprocess_theme for site_identity. <?php print theme('site_identity'); ?>...
Block title combo and 2/3 things