A number of improvements are coming out of the Usability Study at the University of Minnesota. This one is to remove the menu item from the drag 'n drop manage fields screen because it is just too confusing. It's not recognized as a field that they created or control. Behind the scenes we can keep it where it is in core -- adjusted to be right under the title, where ever the title is.

Comments

karens’s picture

karens commented
Component: General » Usability
karens’s picture

karens commented
Status: Active » Fixed

This change was committed.

yched’s picture

yched commented

I committed a slightly different (less intrusive) fix for this : we don't include 'menu' in the list of the 'extra fields' we handle with d-n-d, and we adjust it's weight just below 'title' in form_alter.

catch’s picture

catch
he/him
Primary language English
commented

Although this is easy to change with form alter, iirc one of the participants said they'd actually want to use the dnd to make the menu fieldset less prominent. Was wondering if "title, body, menu" could have 'system provided' somewhere in the empty operations columns on that page instead? If people see system provided, then they'd hopefully realise that they didn't accidentally make that field themselves.

No big deal, but I was pretty excited to see full drag and drop on that page including the stuff that core provides compared to how it worked in D5, would be a shame to lose it outright. Either that or some extra help text on the 'manage fields' page to explain why menu is there.

karens’s picture

karens commented

I'd like to get a vote on this from the people here since that came up so often -- remove menu or add more explanation?

Also, the dnd was showing up for content types without any fields, making it look like you could still rearrange menu, title, and body on those content types, which wouldn't have worked, so my latest commit hides the whole dnd if there are no fields defined.

karens’s picture

karens commented
Status: Fixed » Postponed (maintainer needs more info)

I guess I need to re-active it to get comments :)

catch’s picture

catch
he/him
Primary language English
commented

/// making it look like you could still rearrange menu, title, and body on those content types, which wouldn't have worked
I thought you could do that, so good idea to remove it. The message looks great as well!

Help text suggestion:

Title, Body and Menu Settings are provided by Drupal core. You can customise 'title' and 'body' in the Submission form settings.

yched’s picture

yched commented

/// making it look like you could still rearrange menu, title, and body on those content types, which wouldn't have worked
Er, I thought it could do that too ;-). Can't remember if I actually tested it, though.
Karen, you did see it not working ? If so, maybe it's a bug we could fix, Out of my head, I can't think of any reason why that would not be possible...

I don't have any strong opinion about the 'menu' item. I'm not sure I get why it got promoted out of 'bottom fieldsets' to begin with, I kind of hesitated before including it in list of 'movable' items, attaching it below the title field is fine by me.

+1 on catch's idea to use on of the the empty columns to provide some (non active) information about the module that manages the field.

catch’s picture

catch
he/him
Primary language English
commented

Actually - I would really, really love to be able to move around all node form fieldsets on that page (specifically for fields added by non-cck modules like location and the rest - but even publishing options and stuff like that would be useful sometimes).

That makes for potentially way more confusion though, but IMO a killer feature. Maybe a sub-module which allows you to select which system/module created fieldsets to re-order so admins can configure it?

catch’s picture

catch
he/him
Primary language English
commented
Title: UMN Usability - Remove menu from Manage Fields » Drag and drop on all $content fields, or none?
Category: task » feature
Status: Postponed (maintainer needs more info) » Active

Changing this to a feature request, and marking http://drupal.org/node/135816 as duplicate (which I hope counts as a couple of votes in favour :)

catch’s picture

catch
he/him
Primary language English
commented
Title: Drag and drop on all $content fields, or none? » Drag and drop on all node fieldsets, or just cck?

another go at that title now I've unduplicated the other issue.

karens’s picture

karens commented
Status: Active » Fixed

Since this was originally posted the Manage fields screen was updated. You can now drag n drop all the core 'fields' on the Manage fields screen, and contrib modules who want to make it possible can add themselves to the list of draggable fields.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

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

chiddicks’s picture

chiddicks commented

I've used this hook for a module I just wrote, Node Form Rearrange [http://drupal.org/project/node_form_rearrange].

I'm mentioning it here because this module is geared toward making node form elements rearrangeable - it will be extended in the future to include a other fieldsets (Revision Information, Authoring Information, etc). It could include the Menu fieldset should this be something that the core content module wishes to remove. It uses the CCK drag-and-drop tool to set the weights of those fields.