Saturday 28th April, 2012
10:30am to 10:55am
Have you ever worked on a Drupal project, when you opened the permission admin page and got lost in the sea of checkboxes? Have you ever thought it's not fully clear what is going to happen if you grant a permission to a role, or which permission includes other ones (for instance administer content vs. edit nodes of a content type)? Come to this session, and hear about the proposal that was developed during the Google Summer of Code programme last year, which could potentially solve these issues.
We have all faced this problem. As a site build is progressing, the permission page grows. Your hand is almost shaking when you have to load that page to make some adjustments. Each time you enable a module it provides new permissions, and you really need to know what you are doing, when you grant one of them to your users. Some of these permissions cover others, but the UI doesn't reflect this. In many cases, the granularity doesn't fit for your needs: having an "administer something-type" permission beside the few low-level one is not enough. So you end up granting a too powerful permission to your clients. Just think about the administer users permission.
I started to work on the solution last year, as a Google Summer of Code student with my mentor, Károly 'chx' Négyesi. By the end of the project, we came up with the concept of how we think hierarchy for permissions should work within Drupal. A patch was written for the basic logic, and we made wireframes for the UI. Since then a propotype has been also created for the user interface. In this session I will present the work that has been done so far and the plans for the future, including what it could mean for Drupal 8.
Bálint is a web developer from Hungary who has been working with Drupal since 2007. He was a Google Summer of Code student in 2011, and after the successful project and a core conversation at DrupalCon London he relocated to Gothenburg to join NodeOne. He is mainly focusing on module development, but as a person who likes change, he is also happy to work on usability issues.
Freelance Drupal web developer, amateur squash player, trance and d&b music lover. bio from Twitter
11:30am Case study - Classify by Joel Söderberg
Sign in to add slides, notes or videos to this session