• DrupalAdminInterfaceImprovements

When you try to set up a site during a sprint, you realize how many l ittle things suck abotu the drupal admin interface.

Places people are trying to work on these things:

• http://groups.drupal.org/soc-admin-usability-improvements

• http://drupal.org/project/administration

• http://drupal.org/project/advuser

• http://drupal.org/project/category

Here is a list - please help keep up to date with links to Drupal.org feature-request issues:

Administrative Interface

Taxonomy

1. User should be able to one click delete a term when looking at a vocabulary list /admin/taxonomy/[vid]
2. When you delete and taxonomy term:
   1. drupal should tell you how many nodes are tagged with that term.
   2. offer you a list if you want (which would open admin/node to that term
   3. let you combine the term with another term
3. there should be an option for moving a term (or parent and all it's children) from one vocabulary to another
4. add taxonomy weight setting to the admin/taxonomy screen so you can easily set all taxonomy wieghts
5. add a "disable" taxonomy function, so you could disable taxonomy terms, parents terms, entire vocabularies buch in the same way you can disable a menu or menu item. Why? what if you want to stop using a taxonomy going forward, but don't want to kill the old stuff?
6. Create a taxonomy view that allows for hidden children
   1. If you have a really detailed fine grained heirarchical taxonomy, you might not want to give the uisers an option of browsing all the 2nd 3rd and 4th teri terms, but you want users creating nodes to be able to assign fine grained terms. In this case, parent terms would encompass all their children terms. All terms would be displayed on a node, and clicking anyone would have the same behaviour as you would current experience.
7. Per Node type taxonomy weight: when you are creating content types using cck, you or configuring content type settings, you should be able to override the taxonomy weight and set a taxonomy wieght for a particular vocabulary on a particular content type. So on "directory" nodes "issue" vocab might be a -8 but on, but on articles it might be a +8

Node Administration

1. User should be able to add multiple cireteria in the node filter on admin/node at one time
   1. Filter by date range
   2. filter by author
2. user should be able to sort node list by each column heading and reverse sort if they want
3. there should be a "check all nodes" box

Content Type Administration

• there are two places to adminsiter content types, and niether refers you to the other.
  • /admin/node/types
  • /admin/settings/content-types
• On the admin/settings/content-types screen the user should be bale to admin content type behavior like work flow through a matrix, and not have to edit each one individually.

User Administration

1. Administer user settings in a matrix
   1. User roles
   2. user block setting
   3. user contact forms
2. admin function for resetting and sending a user's password (yeah i know they can just reset it by requesting a new one, but an admin should be able to "reset password and notify")
3. Set user role on user create
4. user roles that users can apply for on signup

Block Administration

1. Add a matrix view for block adminsitration that adds visibility setting, default viz, and enable disable by user choice
2. Add visibility by user role
3. Add a duplicate block function: this would be a link from the block menu, it would create an identical block with all the same settings, and open it to the edit form where you could change details.
4. Add an "enable/disable block title" check box . If you have a block that consists of images, you should be able run the block without a title.

Menu administration

1. Create ability to work in one menu at a time (so if you are working in the heaviest menu, adding menu items, you don't have to scroll all they way down, or find the right menu in the drop down list of parent menu items)
2. Create a multi menu item add form that allows you to add multiple menu items by entering them into a matrix with all necessary fields
3. Duplicate menu function: this would open up a add menu item form, all filled out for the menu you just duplicated, but then you would be able to change specifics
4. duplicate menu item and children: this would open up a menu item add matrix allowing you to change the specifics. Super helpful if you have a number of menu items that have the same children menu items (that go to different links.

Path Alias (URL Alias)

Admin Path Alias

1. Improve ability to browse path aliases
   1. Add an alpha selector
   2. filter path aliases by node type
   3. filter by manually created path aliases vs. path auto created path aliases
   4. Add ability to search for path aliases by partial path alias
   5. this would allow the admin to search for all paths like "*publi*" and get a list of all paths with "publi" in them.
2. Add ability to create multiple path aliases at the same time
3. Add ability to edit / delete multipl path aliases at the same time

Path Auto

1. Add option to delete some auto generated paths en mass
   • this would allow an admin to delete all auto generated paths for a specific content type and then recreate just those paths.

Views

1. Add "Export all Views" option that lets admin export all views and save as a text file.
2. Add "dublicate view" option that duplicates a view (now requires user to export and then import the view)
3. When exporting and then importing a view, html in headers and footers becomes escaped or otherwise malformed.