Closed (won't fix)
Project:
Drupal core
Version:
7.x-dev
Component:
node.module
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Dec 2007 at 01:08 UTC
Updated:
23 Mar 2012 at 18:51 UTC
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".
Comments
Comment #1
Bevan commentedI 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 commentson the node-type settings page and[ ] Comments are Read-Onlyon 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.
Subject, Preview, and Location should be made checkboxes. e.g.
Can this go into drupal6?
Plz tag for newbie.
Comment #2
birdmanx35 commentedChanged to 7.x dev, as this would require string changes, and string changes are frozen.
Comment #3
sun.core commentedTagging. Setting proper status.
Comment #4
Bojhan commentedThere is no clear problem definition or solutions.