![]() Of course, it's possible I could be entirely wrong in my assessment. Group: Group block content (Fancy Tabs block). ![]() Group: Group block content (Basic block).Each plugin shows up automatically in the admin menu with the following links (for example): I think it probably doesn't support that many different submenus. The error may have something to do with the way the Edit Menu page is structured. This was on a fresh import of the database from a different tier, after clearing cache, etc.Īgain, the error appears when navigating to the Edit Menu - Administration page: /admin/structure/menu/manage/admin. The specific plugin that I choose to install has no bearing on whether or not the error occurs, it's just only when I have 10 or more plugins. Then, I uninstalled a different plugin and the error went away. Just now, for example, I picked a random 10th plugin, saw that it caused the error. At first, I thought it was a particular plugin (the Group Block content plugin I referred to in comment #3), but I tried different ones and they alternatively worked and didn't work until I realized there wasn't one plugin in particular. I don't know why but the error seems to only occur if I install 10 or more plugins. The way to reproduce this is by installing a certain number of Group plugins. I think I have an idea of what's causing the problem. For this particular project, I have not been using the Drupal console command line tool-just Drush. Thank your for your help and taking the time to respond. For some reason, even though I had already tried flushing the cache, the uninstall only worked when I reset the codebase back to the last commit-probably something changed on the file system to prevent it from fully uninstalling. When I tried it a few times it would give me a white screen. Unfortunately, uninstalling Group module plugins seems to be a little buggy too. ![]() ![]() until the problem goes away-which is exactly what I did (in my case, it was neither views or modules). From what I have read, the simplest solution is usually removing modules or views, etc. Many times, these kinds of route-does-not-exist error messages are the result of a leftover menu route that is referenced in code but does not appear in the site's route table. For those reading and wondering, this is not a regular module, but a module-specific plugin that appears on /admin/group/types/manage//content (a page that lists content plugins). When I uninstalled it, the bug went away. There's something wrong (EDIT: or so it appeared at the time) with a Group Block content plugin that I had installed for my Group Types. I "solved" the problem for what it's worth. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |