Steps to replicate bug use case: Newbie Drupal Admin was too mindless to check to see if there was an existing module for creating glossaries. :-) With Clean URLs enabled and before installing Glossary module, Drupal admin has already created a static node aliased to http://www.example.com/glossary, in other words, a glossary written as a static Page. Then Admin discovers Glossary module, and attempts to install. Post-installation, the Glossary filter tabs do not appear.

Bug resolution: A closer reading of the documentation shows that Glossary Module is hard coded to use the /glossary URL. Freeing up the /glossary URL fixes the problem.

Suggested fix: While it would probably be possible to write a routine to check whether the /glossary URL is in use and cough up a warning dialog, this seems like an issue that could adequately be resolved by addressing the issue in the module documentation. The steps to install the module should prominently warn that the /glossary URL must not already be in use.

Comment: Very nice module. I was previously maintaining my glossary in a word processor using a set of custom styles and scripts (the latter to create cross-reference links). It still required a fair amount of clean-up in a plain text editor after exporting to HTML before clipping to Drupal. A real pain in the bohunkus to do after ever glossary revision. Using the patch for linking terms used in definitions to their own definition terms has eliminated a lot of work for me and a reduction in errors resulting from having an incompatible app of origin.

Comments

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Assigned: Unassigned » nancydru
Status: Active » Fixed

The documentation has been changed. I added a specific paragraph "Conversion note."

I am interested in how people convert previous types of (particularly HTML) glossaries. During the last GHOP, I approached one of the students about how to automate most of the conversion, but nothing came of it. I may resurrect this task for the new DROP sprint. I still have a site with two larger hard-coded glossaries, one of which I have already converted on a test site but still need to upload.

Marbux’s picture

Marbux commented

I've taken my static page glossary down but would be happy to send you a copy of its HMTL source if it would help in your conversion experiments. Just send me an email at (subtract the trees) marbux pine @ pine gmail. pine com. It's done as an html definition list with each term linked from a table of contents embedded in a three-column, single row table.

A related question: Is it feasible to convert between Glossary module content and G2 Glossary content? My only hesitation about using the Glossary module is the strong likelihood that my glossary may grow to the point where I would have to switch to avoid bogging down Drupal.

Marbux’s picture

Marbux commented

I should have added: My glossary is still fairly small, about 60 term/definition pairs. So conversion isn't a big issue for me. Best on my test cases, it will probably be less than 3 hours work for me to do the job manually using clips and minor editing. I'm aiming to get that done tonight.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented

I honestly don't know that much about G2. The owner has suggested that we may have some common features that we can merge, but that's the extent of it so far.

There are users of Glossary that have huge glossaries, so you probably don't need to worry for some time. Make sure caching is working and the impact is minimal.

nancydru’s picture

nancydru
she/her/hers
Primary language English
Location Boston
commented
Status: Fixed » Closed (fixed)