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 withdrawing my question for the following reason: https://forum.backdropcms.org/comment/8960#comment-8960
Error when trying to check for updates
My hosting is located in a country that blocks numerous online resources, so I am not surprised that updates and modules are unavailable. However, everything works perfectly on a local server...
Unable to run update - fails with Connection timed out
UPDATE: I fixed the errors that I found in the logs. They were related to deleting an old blog content type pulled over from Drupal that was still referenced in one of the layouts. I updated...
missing "add block" in custom layout