When applying the glossary filter to glossary terms, the current term should not be highlighted. It ends up in a silly recursive definition.

Comments

nancydru’s picture

Assigned: Unassigned » nancydru
Status: Active » Closed (won't fix)

Quite some time ago, several people asked for terms to link to other terms. We gave them that. Yes, it might look a bit silly to link to itself, but that is what happens. And, BTW, you can often see this also in dictionaries. I don't, off the top of my head, know of any easy way to stop this, short of rewriting your term's description. Unless a bunch of people jump on this bandwagon, I'm going to mark this "won't fix" and may revisit it in some time in the future.

mariuss’s picture

If you mark it as Won't Fix it will disappear from the list of pending bugs, and it is a valid issue IMO. Please leave it there so it gets some exposure.

Cross linking terms makes perfect sense, I'm glad that this is done. I have never seen in dictionaries terms with self references, can you give me some examples (unless it is a Wiki and that's an issue as well)?

When you apply the filter, you don't get enough context information? If that's the case then maybe we should ask for a feature from Drupal core.

mariuss’s picture

Funny enough, just run into a Drupal feature request that would allow you to fix this:
Context-aware filters

Unfortunately this will probably happen in Drupal 7 only, the soonest.

nancydru’s picture

Status: Closed (won't fix) » Active

I am bringing this one back. I am adding a "default filter" for the glossary overview. It may point to a filter that does not use glossary and therefore turn it off for the overview. I know this is not a complete solution, but it is handy right now.

nancydru’s picture

Status: Active » Fixed

Committed to both branches.

Anonymous’s picture

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.