Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Currently, if the path for a taxonomy menu link contains a fragment (e.g. example#anchor), the menu link is inserted into the database, but is somewhat "corrupted" and is not visible when viewing the actual menu.
This is because the fragment needs to be moved out of the path itself and into the menu link's options array as the 'fragment' key. The same thing is currently done for query strings, but not for fragments.
The attached patch implements this functionality.
Comment | File | Size | Author |
---|---|---|---|
#2 | 2428283-03.patch | 598 bytes | joshmiller |
support-for-anchor-fragment-in-menu-links.patch | 668 bytes | Scott Robertson | |
Comments
Comment #1
jenlamptonCan you describe your use-case for if the path for a taxonomy menu link contains a fragment? IIRC taxonomy menu links are always in the form
taxonomy/term/tid
. Are you using some fancy aliasing? Or, how is a fragment involved?Comment #2
joshmillerHey Jen.
I've inherited the site that Scott originally created this patch for. Couldn't tell you why we ran into this, but I did need to reroll it against 1.x. Feel free to ignore.
Comment #3
joshmillerMost of our taxonomy pages are handled via Views and Solr, so maybe Views requires the fragments for solr facets to filter against?