Open stpaultim opened 3 months ago
I was thinking that this might be a core issue and I opened an issue in the core issue queue.
https://github.com/backdrop/backdrop-issues/issues/6457
However, I now realize that the problem is simply that we are starting with a fully functioning Backdrop CMS site that includes active configuration for the Dashboard module. After the upgrade, the dashboard configuration still exists in the config file, while the database is completely gone and replaced by the Drupal 7 database.
Possible solutions:
1) D2B module looks for and removes any dashboard related configuration during the preparation phase of the upgrade process. (There might be other similiar clean-up tasks that should also be done) 2) D2B enables the Dasbhoard module after the upgrade is complete. Is this possible, or is it too late for the D2B module to do anything at this stage. 3) D2B module creates a new config set of active config files during or immediately before upgrade to make sure that there are not any unnecessary configuration files in the active directory after the upgrade is complete.
After completing an upgrade, I have a dashboard link in my admin menu, but the dashboard page is empty. The problem is that the dashboard module is not enabled.
I don't know where the link is coming from, if the module is not enabled. Should we enable the dashboard module during the update, since the dashboard does provide a nice welcome block to help new users understand Backdrop?