Hi there,

I've created the individual nodes for each question. But in the create and edit functions of the nodes I don't see the field to categorise through taxonomy. I have created the relevant Taxonomy vocabularies. Yes, the module is enabled.

One thing, I am not using taxonomy anywhere else in the site, so i may have turned it off somewhere? The field doesn't appear in any of my other content types either.

Thanks for the assistance.

Jon

Comments

iko’s picture

I had the same problem, but creating a term reference field from the content type edit page solved it. May a maintainer tell me whether this is a good practive, or do you plan to add a FAQ.module-specific reference to faq categories ?

Thanks !

pbuyle’s picture

In Drupal 7, you have to add a Term Reference field to the content-type you want to categorize using terms from your vocabularies.

mortona2k’s picture

I remember having to do this too. However after doing it, I can't manually order the questions. (Not 100% if this is when the problem started).

markusbroman’s picture

I'm having problems with categories as well. I have tied every node with a term in a term reference field but when I go to FAQ page no nodes are listed. Have you guys experienced this? If I disable categories all the nodes are listed.

Any ideas?

stella’s picture

Status: Active » Fixed

There's a few different things mentioned in this thread, so here's the answers to them all:

  • Yes you need to add a term reference field to your faq content type in D7, at least for now. It's still in development, so this may change. Steps are: create your faq vocab(s) and add terms to it; Add a term reference field to your content type for the appropriate vocab; Assign each node to a term; Enable faq categorization in the faq settings.
  • FAQ ordering not working - fixed in another issue, try latest dev version
  • No nodes are listed on the faq page - check your faq category settings and ensure you have assigned a term from your faq vocab(s) to each faq node. See also http://drupal.org/node/294708

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.