Currently, when installing the default installation profile, we have a vocabulary 'Tags', which is automatically added to the content type Article as a field. So far so good. The field name of the reference is taxonomy_tags (taxonomy_VOCABULARY_NAME). This is a bit strange, because every other vocabulary that is added to the content type later on will be named field_SOMETHING, eg field_cars.

I'd suggest to name the default vocabulary field field_tags instead of taxonomy_tags. See the attached patch.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

yched’s picture

Component: install system » taxonomy.module

makes sense IMO. That's a remnant from the time taxo fields were created automatically when a vocab was created. We removed that in #628244: No way to attach the automatically created taxo field.

BarisW’s picture

Status: Active » Needs review

That's what I thought ;)
Please review!

BarisW’s picture

Would anyone be so kind to review the (tiny) patch?

moshe weitzman’s picture

Status: Needs review » Reviewed & tested by the community
Dries’s picture

Status: Reviewed & tested by the community » Fixed

Committed to CVS HEAD.

Status: Fixed » Closed (fixed)

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