After #87 and #480, we might run into more cases where people upgrade Backdrop to newer versions that have included contrib modules in core but leave the respective old contrib module folders in their /modules directory. Now, we already have tried to make sure that these left-over modules are not called, but we can never be really sure of what issues might be caused by leaving duplicate modules both in core and contrib module directories. Can we put some message/warning in place that "nags" people telling them that it is safe and recommended to remove the module folders from /module directory?
GitHub Issue #:
915
Recent comments
I'm really hoping to make this simple change on new content types: https://github.com/backdrop/backdrop-issues/issues/7080 Let's disable the "Display author and date information" by...
February 26th, 2026 - Weekly Meetings
For our DEV meeting: an older bug needs (and could have) a fix. Issue #5729 - Views: Search Filter: On Empty Input "Show None" option Shows All There are 2 pull requests, but one...
February 26th, 2026 - Weekly Meetings
Ruby Text can be a bit of a hassle to edit... Yes, I can imagine that. No idea, how an editor dialog (or whatever) for easier editing of those should look like - in terms of...
Specific tags to work in CKEditor 5