Glossary term does not link to glossary page

I have the same issue, actually. I’m not sure if this is the intended behaviour or not: WP-Glossary might only be putting hovertips but not actual links to the content itself.

Creating a (normal) link on the words, and putting [glossary slug=’xxx’][/glossary] around it makes things even worse: now the link will certainly work, but the hovertips will not.

Like @stephen451, I’d love to have both functionalities: hovertips and a working link to the glossary page — this is because many of my definitions are quite long, include images, etc. and they would be far better seen on its own page. The hovertip is useful, of course, but sometimes it’s not enough.

I think this might fix it.

The shortcodes are handled by class/wpg-shortcode-glossary-class.php

As far as I can understand the code, it tries to find something to search for — a term id, a slug, a word (between the shortcodes) — and if it’s successful, it will assemble a specially crafted A HREF.

On line 56, we have

$href = get_permalink();

which should retrieve the URL to the current page.

Changing this to:

$href = $id ? get_permalink( $id ) : get_permalink();

checks if we have a valid glossary term id. If so, then it places an URL to the glossary term; if not, well, it defaults to the current page’s link (I’m not sure why this is supposed to be useful).

I’ve tried this change on a few glossary entries and it seems to work… but Tom should take a look at this first, there might be some hidden issues with the change which aren’t apparent to me.

Wow! Great answer. It works for me too. I do not actually want the tool tips. The link was not working by itself and I added the tooltip to help find where the fault was.

There is an interesting issue if you hit the back button after going to the definition as you see the tooltip still open. It stays there for a few seconds before it disappears.
Many thanks for your help. Your fix has worked for me. I agree Tom should look so I will leave the issue as unresolved at the moment.

There are other functions in the scope that rely on setup_postdata() function. I was wrong to expect the same from get_permalink().

Good spot (fix coming)!

Thanks, Tom! I’m preparing also a few more minor tweaks, all related to properly supporting translations — I’ll be sending them to you in a bit.

This should be fixed ??