Closed (fixed)
Project:
Drupal core
Version:
7.x-dev
Component:
update system
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Oct 2010 at 01:36 UTC
Updated:
14 Nov 2010 at 03:50 UTC
Jump to comment: Most recent file
Comments
Comment #1
furamag commentedI 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.
Comment #2
jeff veit commentedIt'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.
Comment #3
servantleader commentedI 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.
Comment #4
yched commented"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
Comment #5
jeff veit commentedNow 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.
Comment #6
yched commentedretitling then
Comment #7
yched commentedPatch.
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...
Comment #8
dave reidReasonable and looks good to me.
Comment #9
chx commentedI guess that's true...we want people to update towards a more standard-profile experience and not minimal.
Comment #10
int commentedthe menu critical countdown only count the 7.x-dev version. So change the version.
Comment #11
EvanDonovan commentedAgreed that this is essential.
Comment #12
dries commentedCommitted to CVS HEAD. Thanks.