Not working at all

you can try views bulk operations. We had the idea to add an indexer but no time to write the code actually...maybe there will be some funding for the module soon. Then we will extend it...

Thanks
Ivo

I tried glossify 6.x-3.0-beta11 from 2012-Jul-31; enabled 'glossify' module, 'simplehtmldom API' module and 'hovertip' module; downloaded and extracted 'simplehtmldom' into ./sites/all/libraries/simplehtmldom: added the filter to my default text format and did some configuration at ./admin/settings/glossify/global as seemed appropriate. Result: nothing. Cleared all caches (drush cc all) and rearranged the input filter, still nothing. No error message on the configuration page and no warning at ./admin/reports/status, just nothing.

Replaced glossify 6.x-3.0-beta11 with glossify 6.x-3.x-dev from 2013-Sep-30, checked the default input format ("Glossify filter" was still enabled) and glossify's configuration page. Ran ./update.php and cleared the caches again. Reloaded a sample node multiple times and re-saved it. Still absolutely nothing. Selected all "Content types to be filtered" and "Target content types", checked all "Style of glossary terms". Checked "Make use of the title field of a node" and "Attach 2 additional fields to the selected Node types". Now at the bottom of the test node appeared a h3 section: "Terms referenced: k.A.". No links, no hovertips.

My setup: I have one "glossary" content type. I want all occurences of these content type's node titles to become links (or maybe hovertips) in the other node's texts. The "glossary" content type has nodes with node titles that exacrly match words in the other content types.

According to README.txt, that's exactly what 'glossify' is supposed to do:

1. "Link-FROM" content types - We look for keywords into their text and replace them with links.
2. "Link-TO" content types. (node-title = keyword).

What am I doing fundametally wrong that I do not even get error messages? Or is the current 3.x complety disfunctional? Is it required to downgrade to the 2.x branch as #1 suggested about 3 years ago to use this module?

Unfortunately, the d6 version is pretty much a disaster (completely before my involvement with the module). And at this point I don't anticipate devoting any time to it all unless someone provides a patch. Feel free to reopen with a patch.

@WorldFallz: Yes, on one site I'm using the D7 version, which works quite fine.

However, the majory of my sites are stuck with D6, so I'd still appreciate any help from someone being able to fix the D6 release.

I don't make the decision lightly. My main site is D6 as well and will be for a quite a while longer. However, after literally wasting entire days trying to disentangle the disaster that is the d6 version of this module, I simply had to give up and take it off the site I had originally assumed maintainership in order to use it on.

I'm happy to work with anyone who's willing to take it on or provide patches, but at this point I figure I'll have my very complex d6 site migrated to d8 before I can figure it out. :-(