I'm not sure if this is a bug of by design. Seems like if there are any nodes attached to the glossary term, it will always link to the taxonomy term page.
This seems odd, because to me the whole purpose of attaching a node to a terms is to give it a more detailed definition. So I would expect it to still link to the glossary/* page as specified in the settings.
The way I had to fix it for my site, is I changed the _glossary_get_terms() function SQL query NOT to join to nodes table at all, since it doesn't matter for application whether there are nodes or not. Hate hacking the module code, but I didn't want to make changes to the _glossary_filter_process() logic without first getting some feedback.
Is there a specific reasoning for this? And would it make sense to add an admin setting to override this?
Comments
Comment #1
arlmedia commentedWe also had that problem. It does not seem to make any sense, to change the glossayr target link after adding nodes to the glossary definition. Also URL-Aliasses arr different for taxonomy and glossary target pages.
We had to fork changed the module - as it was used on http://gelenk-doktor.de:
Original code:
Our version:
After Cache-Update the links to glossary terms were unified. to
Comment #2
nancydru