-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closes #2315: Downgrade menu_block to 8.x-1.7 until we have a better solution for empty sidebars getting rendered. #2320
Conversation
…solution for empty sidebars getting rendered.
I've tested this with both system menu blocks and custom menu blocks. In 2.5.5 custom menu blocks cause the ghost block to appear, however , the system menu blocks function as expected. Just saying this brings the functionality back to how it was in 2.5.5, which is what we want. |
Other notes: The patch we are using is likely superceded by issue 3007225 on drupal.org The patches in issue 3271218 on drupal.org do not work with menu_block 1.10 Yet another issue about this https://www.drupal.org/project/menu_block/issues/3271218 This is all because of a 13 year old issue for Drupal Core https://www.drupal.org/project/drupal/issues/953034 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested in Probo just in case: I created a new system menu, added the menu as a block to the Sidebar First region, and disabled the default Quickstart sidebar menu block. With the Initial visibility level set to 1, the new sidebar block appears on all pages. With the Initial visibility level set to 2, the sidebar properly appears only on the page which is included in the new menu.
…solution for empty sidebars getting rendered. (#2320)
Description
Downgrades menu_block back to 8.x-1.7 (the version used in Quickstart 2.5.x). This should resolve the immediate problems identified in issue #2315 for now for sites upgrading to Quickstart 2.6.x and give us time to find a better solution to deal with the larger core issue that is the underlying cause of the issue: https://www.drupal.org/project/drupal/issues/953034
This reverts PR #2049.
Verified that no database or config schema changes exist between 8.x-1.7 and 8.x-1.10.
Related issues
Closes #2315
How to test
Types of changes
Arizona Quickstart (install profile, custom modules, custom theme)
Drupal core
Drupal contrib projects
Checklist