Closed (fixed)
Project:
Context Active Trail
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
12 Jun 2017 at 19:32 UTC
Updated:
25 Jan 2021 at 22:14 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
jigariusCouldn't understand properly. Can you give some more details about whats happening? Maybe include some screenshots or describe in detail what your configurations are, etc?
Comment #3
jigariusComment #4
daniel korteI had this same issue. The issue happens when there are two separate menus each with their own system menu block showing in the same region along with an active trail set up for a menu item existing in one of the menus (but not the other menu). What happens is the Context active trail module does not validate that the active trail it is returning exists in the menu that is requesting the active trail so both system menu blocks actually end up being built out with the menu that the active trail exists in. This is because the SystemMenuBlock build function relies on the parameters that the Context active trail module (incorrectly) alters to build the menu. This patch adds the menu check.
Comment #5
freelockRan into the same issue, and confirmed the diagnosis and that the patch works.
Comment #7
jigarius