It appears that you can create Taxonomies, but that's where it ends. There doesn't appear to be any way to apply them to content types unless you turn on Fields UI. There's no hint that that's what you need to do, so Taxonomies seem pointless in the base installation.

This is a regression from D6 where you could apply taxonomies to content types.

CommentFileSizeAuthor
#7 D6_upgrade_field_ui.patch503 bytesyched

Comments

furamag’s picture

I don't think this issue is a bug. There are few issues about this new functionality. For example http://drupal.org/node/937728. It looks like this should be "feature request" or "support request" but not bug.

jeff veit’s picture

It's a bug in the beta because the default installation profile doesn't include Fields UI being turned on.

So you can make taxonomies, but unless you have Fields UI turned on, which you won't know to do if you are testing Drupal for the first time; you won't be able to do anything at all with your newly created taxo.

You might as well have Taxo module turned off. At least that wouldn't introduce any confusion about the point of taxonomies that you can't use for anything.

Or have Fields UI turned on by default, which probably makes more sense.
Or have another mechanism, similar to D6, to apply taxos when Fields UI is off but Taxo is on.
Or make Taxo a dependent of Fields UI.

servantleader’s picture

I expect new users to be very frustrated with this. It at least needs a message that tells them what they have to do (enable Fields UI, add a Taxonomy reference field, etc.). It is these kind of bad experiences that give Drupal a reputation of being non user friendly.
When I stared with Drupal 6, I wasted hours trying to figure out how to upload photos because there was an admin/settings/image-toolkit page that was completely useless. I was very close to giving up on Drupal all together. I am certain thousands of others had the same experience.

yched’s picture

"It's a bug in the beta because the default installation profile doesn't include Fields UI being turned on."

?

field_ui is enabled in the standard profile, see profiles/standard/standard.info

jeff veit’s picture

Now that is odd. I kept a list of what I had to do, and Fields UI was definitely switched off. I wonder if it could have been turned off by the theme. No wait: it was an upgrade - so Drupal 6 doesn't have a Fields UI. Are profile modules turned on during an upgrade? If not, that would be why. In which case every upgrade from D6 will seem to lose functionality.

yched’s picture

Title: No way to apply a taxonomy to a content type without Fields UI » Field UI not enabled on a D6 upgrade ?
Component: taxonomy.module » update system

retitling then

yched’s picture

Priority: Normal » Critical
Status: Active » Needs review
StatusFileSize
new503 bytes

Patch.

That's critical, IMO - as in : D7-1.0 cannot leave D6 upgraded sites without a Field UI, since this is the central hub for basic D6 core operations such as : edit 'body' settings, set teaser trim length, assign vocabs to node types...

dave reid’s picture

Status: Needs review » Reviewed & tested by the community

Reasonable and looks good to me.

chx’s picture

I guess that's true...we want people to update towards a more standard-profile experience and not minimal.

int’s picture

the menu critical countdown only count the 7.x-dev version. So change the version.

EvanDonovan’s picture

Version: 7.0-beta1 » 7.x-dev

Agreed that this is essential.

dries’s picture

Status: Reviewed & tested by the community » Fixed

Committed to CVS HEAD. Thanks.

Status: Fixed » Closed (fixed)

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