Thought I'd share this for others who are upgrading from Drupal 7 to Backdrop.
Sometimes after upgrading the admin menu could have menu items in the wrong place. Usually this is because the menu was probably messed up on your Drupal 7 site. If you're okay with losing the custom menu items in the "management" menu, this is what you need to do to reset it. (Following this thread https://drupal.stackexchange.com/questions/48515/how-to-completely-wipe-and-rebuild-drupal-menus).
I'm going to take the easiest approach for most people. (More experts may want to do this via the CLI).
- Backup your database!
- Download devel module and install. https://backdropcms.org/project/devel
- Go to Development > Execute PHP (/admin/devel/php).
- Then execute the following:
db_query("DELETE FROM {menu_links} WHERE module = 'system'");
db_query("DELETE FROM {menu_links} WHERE menu_name = 'management'");
menu_rebuild();
The admin menu should now be reset and look more normal.
Recent comments
Interesting question. I see that style of conditional logic regularly in Backdrop core and contrib. I think the technical term for that kind of boolean is "truthy" or "falsy" ("All values...
Is this a good example of Backdrop CMS programming?
Thanks, I wasn't aware of that. That goes back to D7 ways! I do like that these config files are JSONish, and so I can edit them easily by hand (for doing bulk substitution), which is painful in...
Views JSON config files location
Hi @onyx. When you prepare your module files you can add the config for those views into the module folder under config. When someone installs the module then the config is copied into their...
Views JSON config files location
@onyx - I do not have a good answer for you. Remember, BackdropCMS now allows you to store all of your config in the database, if you prefer. https://docs.backdropcms.org/change...
Views JSON config files location
Thanks, I see! So you're trying the same method as I did. At the moment, I don't have ideas why it should fail on your site. Maybe have a look at the database log (admin/reports/dblog)?
Error upgrading