Steps to reproduce: Try to create a new content type and then expand "comment settings" - wow.

This is just overwhelming. As some default options really make sense and are not very likely to be changed it was suggested at [1] to move them into a new fieldset called "advanced".

[1] http://groups.drupal.org/node/7043

Comments

Bevan’s picture

I don't think fieldsets are a good solution here. This leads to 'fieldset overkill syndrome'. Many settings only make sense in conjunction with other settings. e.g. None of the settings make sense if comments are disabled. So why show them while comments are disabled? Put the rest of the settings, all of which are 'advanced' (except for maybe 'flat/threaded' and 'Location of comment submission form'), into a new settings page just for comments.

Read/Write/Disabled should be split into [ ] Enable comments on the node-type settings page and [ ] Comments are Read-Only on the comment settings page.

Also, many of the settings could be much simpler. eg. the flat/threaded/expanded collapsed settings has four radio buttons and is much easier to understand with two checkboxes. e.g.

[ ] Collapsed
- Don't display the body of the comment

[ ] Threaded
- Keep replies together

Subject, Preview, and Location should be made checkboxes. e.g.

[ ] Enable Subject field for comments
[ ] Require commenter to preview
[ ] Display comment form on same page

Can this go into drupal6?

Plz tag for newbie.

birdmanx35’s picture

Version: 6.x-dev » 7.x-dev

Changed to 7.x dev, as this would require string changes, and string changes are frozen.

sun.core’s picture

Title: "Create Content Type" - move some comment options into a new fieldset » UX: Content Type comment options
Status: Postponed (maintainer needs more info) » Active
Issue tags: +Needs usability review, +Usability

Tagging. Setting proper status.

Bojhan’s picture

Status: Active » Closed (won't fix)
Issue tags: -Needs usability review

There is no clear problem definition or solutions.