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
Thank you both for your suggestions. Yeah, I'll give TinyMCE a try... better than trying to fight that behemoth CKEditor 5. The TinyMCE page says it can "co-exist with CKEditor" which is...
Specific tags to work in CKEditor 5
The specific tags I need are "<ruby>" and "<rt>" Wow, yeah, that's a pain with CKEditor5. A custom plugin, for sure, but no clue, what the code has to look like...
Specific tags to work in CKEditor 5
I think maybe the problem is with CKEditor stripping the tags - it can be more aggressive than what you would expect from the text format settings. I copied your examples into an example page...
Specific tags to work in CKEditor 5