Moved here from http://drupal.org/node/222367#comment-762256
It is another way of trying to improve the access control page.
It is incredibly long and serial now, needs endless scrolling.

Everybody is invited to provide different ideas.
I made some mockups to start.

Other relevant pages:
http://webchick.net/node/21
http://drupal.org/node/229193

Paradigms I tried to apply:

  • Try to get as much as possible on the page without scrolling ("above the fold")
    in order to
  • Get everything at one glance ideally
  • Use structuring Elements like font size, color, weight and background colors to have a clear hierarchy

What's the status here? Well - surely everyone's gotta recover from Boston ;)
I'd love to see your Ideas.

Well, I could not wait. So I made some mockups. They are inspired by the Modules overview page on Joomla.org, as cited here: http://groups.drupal.org/node/9568

Attached my mockups. Should be self-explaining.
It is supposed to be done using Thickbox. I don't believe overlays are always a good solution, would prefer to have a fixed region for the settings like in Views 2 Ui. But as the table with all the modules settings is so huge - it is just not possible without scrolling. I always hate the slow loading time of overlays in thickbox. But maybe this can be optimized.

Concerning the rendering of the multiple columns: I know that CSS3 is not quite here yet. But using Javascript it can be done, I've found a nice script: http://randysimons.com/pagina_129_NL.xhtml and it appears to work: http://randysimons.com/overige/multicolumn/

CommentFileSizeAuthor
#1 Screenshot - 086.jpg236.69 KBeigentor
#1 Screenshot - 088.jpg190.57 KBeigentor

Comments

eigentor’s picture

Version: 6.1 »
StatusFileSize
new190.57 KB
new236.69 KB

File attachments did not work on original post

catch’s picture

I'd be very reluctant to change this page fundamentally since it was the only page that just about everyone in formal usability testing immediately grokked. However I agree it's increasingly long and unwieldy at the moment.

Note that there are already descriptions for each permission in D7.

What I'd like to see:

Roles ordered by number of permissions
Filtering by role available from the permissions page rather than just user/roles (actually I wouldn't mind the roles admin in a collapsed fieldset at the top of the page).
Filtering by module - the lightbox thing in your screenshot does this, but ideally we'd have a role/module argument on the permissions page. Then you could be directed straight to that page after installing a module etc.

admin/user/permissions - same as now with maybe a couple of shortcuts up top
admin/user/permission/1 - permissions for "role 1"
admin/user/permissions/node - permissions for the node module
admin/user/permissions/node/1 permisions for "role 1" for the node module.

eigentor’s picture

I get the point about the UMN Test. Must have been quite a relief to have a page people did not get lost in...

Well my idas are mainly from the point of view of a graphic designer trying to get an optical structure. The point you make with being directed to the permission page seems quite important to me, since this is often the source of errors. Same with settings page. I spent quite some time looking for the settings for the del.icio.us module... 8-O

Question: does one normally just set the rights for one role - I think one does. What is hard to handle without massive scrolling m.e. is the overview of all roles in a table. But still it should be there in some way. At the moment it is not there because of - massive scrolling ;)

What is also missing to me is a semantic structuring of the modules as an alternative to alphabetic. All modules concerning image manipulation could be grouped. In my example it is clearly visible with the very numbrous übercart modules.

This thread is indended by me rather brainstorming-like than fixing an issue, so ideas and mockups are welcome, in the end some great ideas can arise out of that. There is more than one solution.

catch’s picture

// Must have been quite a relief to have a page people did not get lost in...

Oh yes!

// What is also missing to me is a semantic structuring of the modules as an alternative to alphabetic.

Yes, definitely. Also permissions within modules are grouped alphabetically at the moment, which results in great stuff like "delete revisions" appearing in the middle of all the "delete any" "delete all" "edit any" list, not to mention unpredictable grouping elsewhere.

If we rework the top level admin categories then we could maybe also group module permissions by those categories? I have no idea how that'd look in practice though.

Just to note that there's currently a patch for drilling down on specific permissions which should help with at least one aspect of the 'sea of checkboxes' problem: http://drupal.org/node/229193

eigentor’s picture

From the discussion and experiences from UMN Testing the following idea comes to me: How to integrate Modules Page and Access control into one interface? Sure there has to be thought how to do this, because one giant page would even detoriate usability.

But the - hopefully arising - way of thinking of tasks and workflow rather than pages makes it logical. You activate a module - you check access settings next. Also, you find a link to setings page and help pages and documentation on d.o.

What I think of is something like Views2 Interface - separate pages for every Module that are integrated into a big survey page similar to my first mockup. You click on a Modules name - you get all settings (access, activation status, a link to the modules options - in one integrated interface).

I think I'll mock that up soon.

sutharsan’s picture

Project: » Drupal core
Version: » 7.x-dev
Component: other » usability

Moving issues from User experience project to Drupal core usability component.

Tor Arne Thune’s picture

Version: 7.x-dev » 8.x-dev
Component: usability » ajax system
Tor Arne Thune’s picture

Component: ajax system » user interface text
valthebald’s picture

Version: 8.x-dev » 9.x-dev

Bumping version

catch’s picture

Title: Create ideas for a new layout of Access control page » Create ideas for a new layout of permissions page
Version: 9.x-dev » 8.1.x-dev
Category: Task » Plan
Status: Active » Postponed

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

quietone’s picture

Assigned: eigentor » Unassigned
Status: Postponed » Closed (duplicate)
Related issues: +#1765576: Redesign Permissions Page

This is a duplicate of another issue, a later one, #1765576: Redesign Permissions Page The later one has more discussion, references etc.

Therefore closing this as a duplicate.