@quicksketch brought this up in https://github.com/backdrop/backdrop-issues/issues/478#issuecomment-1394...
At this point is it likely or worth worrying about a site that has had two or more of these modules installed, and so would be getting more than one of these (rather long) messages?
These messages are copy-paste with some adjustments (module name, change notification and link etc.):
Backdrop core now provides a bundled
[module_name]module. A different copy of[module_name]module has been located at[module/path]. Remove this module from your installation to use new [module_name] module. For more information see the[module_change_notification_link].
I propose we consolidate these messages when more than one such merged-in-core module is detected to something along the lines of:
Some of the contributed modules used in this Backdrop installation are now bundled with core. Remove these modules from your installation to use the new ones. For more information, see the respective change notification for each module listed below: -
[module1_name]at[module1_path][module1_change_notification_link]-[module2_name]at[module2_path][module2_change_notification_link]- ...
Recent comments
"why are these tags only relevant for admins?" I'm allowing the editor as well. That being said, Ruby Text can be a bit of a hassle to edit... easy to accidentally delete a tag or part of a...
Specific tags to work in CKEditor 5
Out of curiosity: why are these tags only relevant for admins? Don't "regular" editors on that site also need them under circumstances? Yes, the editors play nicely, no problem to...
Specific tags to work in CKEditor 5
Worked like a charm! Exactly what I envisioned... now I can edit the ruby text right in the editor, sweet:) Thank you! For those who may have a similar issue, try TinyMCE, create a new "text...
Specific tags to work in CKEditor 5