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
I agree with @yorkshirepudding for new sites. Existing sites that use this "long text with summary" functionality already... not sure. There is an old core issue around this, too, it looks...
Use text editors in Summary Field
I always do a separate summary field for these reasons: Avoids the UI cludge of having either a summary or a trimmed value of body Allows summary to be mandatory...
Use text editors in Summary Field
It seems that while the summary field does not have a WYSIWYG editor. It does have the same text format as the main body field. Cutting and pasting content from the body field does not...
Use text editors in Summary Field