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 am considering migrating my drupal 7 website to backdrop. Hi @seamus, I would like to offer my professional services for migration to BackdropCMS. Please connect If...
drupal 7 to backdrop migration
Restore Newsletter Subscriptions from a Database Backup One of my websites was affected by the Simplenews issue, and there were many incorrectly disabled newsletter subscriptions of '...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled
This is the report about the recently discovered bug: https://github.com/backdrop-contrib/simplenews/issues/83. First, how do you know if your site is affected? In other words: Are there...
Re-enable Simplenews newsletter subscriptions that had been erroneously disabled