I've been away from Drupal for some time now and it's showing. I set up a new Drupal 7 installation today using the standard installation profile. One of the first things I tried to do was create a custom content type for images. I created an image content type and added the image field from the article content type without any problems.

When I tried to do the same for the tags field however, I got a page not found error. Going back to the manage fields tab I saw the following error.

Inactive fields are not shown unless their providing modules are enabled. The following fields are not enabled:
* Tags (field_tags) field requires the Autocomplete term widget (tagging) widget provided by taxonomy module

I checked and the taxonomy module is enabled, and of course the field works just fine in the article content type. Any ideas on what's wrong?

Comments

Cybergarou’s picture

Cybergarou commented
Title: Unable to add the existing field 'tags' to a new content type » Adding field 'tags' breaks all new fields
Category: support » bug
Priority: Normal » Major

So this wasn't just a fluke, I deleted everything and started over from scratch. The instant I try to add the tags field to a new content type I get the same error. Furthermore, I've also realized that after trying to add this field I am no longer able to add any fields. I have even tried adding the existing image field to another new content type and it spits out the same error.

It's still possible I'm doing something wrong, but nothing in the documentation indicates what that could be.

montesq’s picture

montesq commented

I can't reproduce on 7.x-dev with the information you gave above.
Could you try on your side with the last cvs version -> http://drupal.org/node/156281 ?
However, I don't find any trace of such an issue in the fixed issue queue...

Cybergarou’s picture

Cybergarou commented

I tried using the last cvs version and saw the same thing. I'll provide more detailed notes of what I did.

  1. Standard install profile (no changes here)
  2. Add content type 'Image' (uncheck promote to front page and make comments closed)
  3. Save and add fields
  4. Add existing field field_image (used Image for the label)
  5. Save
  6. Make the field required, set the file directory to images, give it a maximum resolution and a maximum upload size, select the bar with progress meter progress indicator. Save the field.
  7. Add existing field field_tags (Used Tags for the label, Autocomplete term for the widget)
  8. Save (At this point, page not found is returned.)
  9. Go back to the manage fields page to see the inactive fields error and try adding more fields to see more.

Oddly enough, I tried adding the two existing fields in the opposite order and I was able to add the tags field, but adding the image field broke everything. Obviously it's not adding that particular field that causes the problem, but rather the process I went through.

droplet’s picture

droplet commented

I can't reproduce too.

can you simplify your steps (keeps most of them to default setting) and reduce factors or its necessary to bring out the problem?

Cybergarou’s picture

Cybergarou commented
Status: Active » Closed (cannot reproduce)

All I need to do to get this error is add two fields to a content type. I can leave everything with the default values.

This appears to be specific to my server configuration; MySQL 5.1.30, PHP 5.2.17, and Apache 2.2.11. I didn't see this error when I tried installing on the latest version of Server2go. I'll try upgrading as much as I can, but PHP 5.3 breaks some of my older sites so I may have to stick with Drupal 6.

Unless someone plans on recreating my server environment, I'm closing this as something that can't be reproduced.

Cybergarou’s picture

Cybergarou commented

Upgrading resolved the issue. The requirements for Drupal 7 may need to be reviewed to make sure they are still valid. Just as a final note, here are the previous versions and the upgraded versions of my server software. (My PHP upgrade didn't work at first since the installer failed to update the directory, so the PHP version could still be the issue.)

MySQL 5.1.30 -> 5.1.55
PHP 5.2.10 -> 5.2.17
Apache 2.2.11 -> 2.2.17