- last update
over 1 year ago Patch Failed to Apply - πΊπΈUnited States W01F
Same issue as original poster - don't understand why this functionality was built into the primary menu, but not the secondary...
You don't have to use it. You can keep the user menu as simple as you want. But having it be a hassle to duplicate something already present by default in the other menu is a pain. I'm currently seeing how I can override the menu--secondary-menu.html.twig file to have the same button wrapping hoping that does the trick.
Or maybe it'll be easier to create a custom user menu and just replace the default one? Obviously neither solution is ideal for such a relatively low weight "feature" (when it already exists literally next door).
In response to Mike's #21 β¨ Olivero: Support second-level navigation submenus on secondary menu Needs work ...why not? Please provide some rationale/background. Accessibility? Potential for confusion? I'm reaching here trying to understand. We absolutely appreciate the enormity of hard work and amazing innovation/triumphs of the new themes and the teams that have bled for these. Personally, I'm using them everywhere on every site I have. But "we don't currently support" by itself, with no context, in any context, is a non-answer, doesn't engage the community, and ultimately disserves the amazing work you've already done. #everythingsharedwithlove