I have set this up on no less than 3 site but I am having terrible trouble today.
I have followed the instructions to the letter however I am getting this message when accessing /glossary
No applicable vocabularies were found, please check your settings.
How do you make the vocab applicable?
Comments
Comment #1
Gabrieles commentedSame here.
When I installed the module I did not have any Glossary dictionary. I created one, but with no effect. I have no errors logged.
A quick google search for "No applicable vocabularies were found, please check your settings." shows 232 results, I guess this problem is quite common.
I am using Drupal 6.10.
Comment #2
flamik commentedI have the same problem on http://neuropsychologia.org/glossary . Is anybody working on this issue?
Comment #3
Anonymous (not verified) commentedsame for me in 6.x.1.6.
even added a new vocabulary and added some terms. no effect.
did i miss sth in the guidelines?? strange..
[update]
after playing around and leaving for other stuff, all in a sudden, the appropriate section for choosing the vocabularies showed up under the input filter tab in the glossary settings.
maybe clearing caches or just waiting, or posting test posts did it, no clue, but now it´s there.
so, first step is to enable one of your input filters and then ... well, for me now it works.
Comment #4
Anonymous (not verified) commentedComment #5
quinns commentedTry running cron and emptying all your site caches. That cleared it up for me.
Comment #6
udig commentedBased on #3...
1. Clear all cache
2. Create a vocabulary + terms
3. Go to Site Configuration-> input formats->
. Enable the glossary filter there.
4. Go back to the Glossary settings ->
Tab. Over there you should see an empty check box with the vocabulary you created earlier. turn it on.
5. Go to the /glossary. Glossary will start rock for you!
Comment #7
boabjohn commentedSorry but #6 is hardly a "fix"? Looks like a great module, but come on! With the google results at #1 from over a year ago now exceeding 1800 (!) it would seem like this little issue is actually a killer.
I have a fresh install of D6.19, unpatched, and the latest views/ctools/panels running sweetly.
The glossary was set up as instructed, and 30+0 terms, synonyms and related terms all imported.
Then we get to the settings, and no checkbox!! Caches cleared, cron run, more content added to other node types, scoured the database for obvious variables hanging loose...nada.
PLEASE: have a look/suggest someplace to peer/ask for debug info/provide your bankl account details...
Look if someone can fix this problem you could probably sell it to the 1800+ sites that have dead glossary installs right now!
sigh.
and yes: much gratitude and respect for your time to put the module together in the first place...
Comment #8
boabjohn commentedOkay sorry for the evil vibe...it was very late night and really there's no excuse to be rude.
So: is there *any* possibility that someone can come up with a way to force the glossary taxonomy to connect with the glossary module? I'm happy to force a variable at the database level...just have no idea where to look.
Very keen for some assistance...and am prepared to contribute in whatever way I can.
Thanks in advance.
Comment #9
boabjohn commentedhmmm. bump? too much excitement in the D7 world?
Comment #10
quinnanya commentedI was really confused too, when I stumbled onto this thread. Here's a revision to step 4 in post #6:
After you've enabled glossary for the "full html" and/or "filtered html" formats (edit the input format, and check the "glossary" box), go into the Glossary settings. There's two tabs there-- one for "full html" and one for "filtered html". If you go to the tab for one of the input settings you've enabled "glossary" on, you can select the vocabularies to use for the glossary. It seems like you could enable different vocabularies for the glossary for each input format.
I added a custom input format, and after I cleared all the caches (including the site cache), that showed up as an option in the glossary settings too.
Does that help?
Comment #11
nancydru