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
Hi Kevin I am interested assisting you developing a theme by cloning feature from existing WordPress website. Please let me know your suitable time to discuss further...
Create a theme from existing website
I've updated the Zulip link in both places I found it. No need to post again, unless you have something new to say. We'll pull together feedback from all the sources.
Backdrop CMS Core Priorities
Should we post here again, what we posted over there? Or would that unnecessarily duplicate things? The link to a Zulip thread in this initial post leads to an internal one, but there's...
Backdrop CMS Core Priorities