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'll be very happy to test this and will report back.
Database update warning - but no pending updates
For anyone interested in an improvement to the Status report that should help with this, please see this issue and the associated pull request: https://github.com/backdrop/backdrop-issues/...
Database update warning - but no pending updates
@paucku I note from this issue here: https://github.com/backdrop-contrib/domain/issues/71 That you started getting this config formatting after changing the module to what Chat...
I need to understand how active and staging folders work โ configuration management