Problem/Motivation
A new user to this module but failing to get it working, despite following instructions at
https://www.drupal.org/project/term_glossary
albeit for v3 (latest on said page)
Firstly there is no indication that I need to go to Admin -> Structure -> Taxonomy to edit (or add) a 'vocabulary'. I have done this and added two simple terms (that I expect to be 'underlined' when I hoover in a page and the explanation of that term to appear)
However once I have done so and then gone to Admin -> Structure -> Content Types -> (eg) Basic Page & enabled "Term Glossary" I am not seeing any expected 'underline' and no explanation appears
Proposed resolution
Provide clear step-by-step instructions, perhaps with graphical illustrations
Issue fork term_glossary-3538785
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
mably commentedHi @mkbane, I'm one of the module's maintainer.
Any documentation improvements are welcome.
Where are you stuck exactly? Could you provide some screenshot of your configuration screen ? Have you checked the README file?
We need more info to be able to help.
Comment #4
mably commentedAdded a few elements to the README file in this issue's MR.
Comment #6
mably commentedComment #7
mably commentedComment #9
mkbane commentedapologies @mably for my delay (I didn't get any email notification and (hands-up!) forgot to check back and look for myself).
However, this is still an issue. i have attempted to follow the README but am not getting any glossary entries.
I humbly suggest that the "Go to the display options of the text fields you want to parse in the entity
display configuration forms and check the option Enable term glossary." is not particularly clear as to where this option is.
My site is GreenCompute.UK, I have (I think!) enabled a glossary for "ChatGPT" including on page
https://greencompute.uk/Footprints/AI
but nothing happens (no underline, nothing when i hoover over it)
Happy to share specific page configs if you let me know what's useful
Comment #10
mably commentedCould you describe in details what you have done so far so I can check if you missed a step?
Comment #11
mkbane commentedI have the module installed.
I have created a GreenSoftware vocab with a term ChatGPT (how to add screenshot here?)
The phrase ChatGPT is on page https://greencompute.uk/Footprints/AI which is a Basic Page
In https://greencompute.uk/admin/structure/types/manage/page/fields I have added reuse an existing field and can see Entity Reference, Reference Type: Taxonomy Term, Vocabulary: GreenSoftware (with Label "Tags", and I have checked Vocabulary "GreenSoftware")
In admin/config/glossary I have GreenSoftware selected and have tried a couple of the integration types (left at their default config)
Comment #12
mably commentedIt looks like you missed the "Manage display" step on your "body" field:
Comment #13
mkbane commentedAh, that screenshot of yours is useful. It is now working :)
I think the phase "Go to the display options of the text fields you want to parse in the entity
display configuration forms and check the option Enable term glossary." on the README would benefit from a screenshot
Comment #14
mably commented@mkbane looks like it's working now :)
Feel free to make any suggestions to improve the documentation.
Comment #15
mkbane commentedYes works now. I got lost at the "Go to the display options of the text fields you want to parse in the entity
display configuration forms and check the option Enable term glossary." so screenshots would have helped (and maybe more exact names of Drupal pages?). with thanks! m
Comment #16
mably commentedFeel free to suggest a better wording.
I'll update the readme file accordingly.
Comment #17
mkbane commented@mably it seems to work for Basic Pages but something non-deterministic seemed to happen re Articles eg
e.g. see https://greencompute.uk/Measurement/CarbonFootprint
It felt like I had to set the Manage Display a couple of times...
Comment #18
mably commentedIt seems to be working fine from here.
May be a cache problem.