I can no longer find the configuration setting that allowed me to set which vocabulary should be used for the biblio keywords. Can you tell me where it is now? Many thanks.

Comments

rjerome’s picture

It's now done automatically by the install file. Keywords are only stored in the taxonomy vocabulary now, so you should already have a keyword vocabulary defined, if not it's a bug.

gustav’s picture

In the old version I was able to choose one of my existing vocabularies. Is that no longer possible now?

rjerome’s picture

Not currently, although I guess there is no reason I couldn't either

  1. Allow the user to select a vocabulary other than the "default"
  2. Put the keywords in the default + another user selected vocabulary

What should happen on update is that the vocabulary which you had previously selected should have been converted to the new keyword vocabulary. Now that I've said this and you have raised the issue, I can see the danger in this approach, since the previous vocabulary may have had other uses. Am I correct in this assumption?

gustav’s picture

Category: support » feature

I did not try the upgrade but instead reinstalled the module. But yes, you are correct, the original vocabulary had other uses. In fact, I was using only one free-tagging vocabulary for all content types. I do not want the biblio nodes to have a separate free-tagging vocabulary. So, yes, allowing the user to select the vocabulary would be nice. I am changing this issue to a feature request.

liam morland’s picture

Issue summary: View changes
Status: Active » Closed (outdated)

This version is no longer maintained. If this issue is still relevant to the Drupal 7 version, please re-open and provide details.