Problem/Motivation

This issue is basically a copy of this issue https://www.drupal.org/node/2631468. Because Superfish extends the SystemMenuBlock class the bug appears when using the superfish module as well.
The problem is the fact that setting an initial menu shows menu items that have parents other than the page the user is on.

Proposed solution

Add the patched code from the original issue to the Superfish block build code.

CommentFileSizeAuthor
superfish_initial_menu_level.patch1.34 KBwillem_
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

willem_ created an issue. See original summary.

Arnoldski’s picture

This patch worked for me! Thanks!

xenophyle’s picture

Yes, this worked for me too

mehrpadin’s picture

Hey there,

Are you experiencing this with D8.5.5 and the latest Superfish dev release? because I've just tested and it's working just fine. Thanks.

xenophyle’s picture

No, sorry, I am using 8.x-1.2. I was assuming it was still a bug since the ticket was active. I guess we can resolve this one. Thanks!

xenophyle’s picture

Oh, I was wrong: The dev release doesn't seem to fix the bug reported here. It might not be described clearly enough.

Parent 1
|_ Child 1-1
|_ Child 1-2
|_ Child 1-3
Parent 2
|_ Child 2-1
|_ Child 2-2
|_ Child 2-3
Parent 3
|_ Child 3-1
|_ Child 3-2
|_ Child 3-3

I have initial visibility level = 2 and levels to display = 2.

If I am on page Child 3-1, I see not just Child 3-1, Child 3-2, and Child 3-3 in the menu, but all Child items. The patch addresses that.

ivnish’s picture

Status: Active » Needs review
LOBsTerr’s picture

Status: Needs review » Needs work

Patch can't be applied anymore

mrinalini9’s picture

Status: Needs work » Needs review

Hi,

The source code in the above attached patch has already been merged to 8.x-1.x branch, that's why the patch is not applicable anymore.

Thanks!

LOBsTerr’s picture

Status: Needs review » Closed (won't fix)