Describe your issue or idea
This is a follow-up to #2842 where we realized that a lot of people were upgrading from Drupal to Backdrop in a way that will result in broken sites.
The root of the problem, it seems, is that people want to update core before contrib, and contrib modules often require their updates to be run between two core updates.
One way we might mitigate this problem is to at least let people know that some modules might be missing by setting a warning at the top of the update page. We could check for missing modules by:
* Check the system table for all modules. Check the modules location(s) to see which modules are present. Compare the two.
* Check if there are tables in the database which are not defined by a hook_schema.
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