Problem/Motivation

Currently there are usecases where we list system/build-in elements(say configuration entity) and custom elements on a single page. For example

User roles page has build-in roles anonymous & authenticated and any custom role(s) added by user.

Proposed resolution

As @webchick proposed at #2119903-25: Show locked date formats in the UI, we can follow what we got in views UI or something similar. Here is a typical outcome:
Current roles UI:

proposed roles UI:

Current date format UI:

proposed date format UI:

Remaining tasks

Discuss the design

User interface changes

Yes, it will change few pages with the scenarios mentioned above.

API changes

N/A

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

vijaycs85’s picture

Issue tags: +D8UX usability
alexrayu’s picture

FileSize
5.25 KB
9.38 KB
8.86 KB

Some ideas. "Locked" may be misleading, sounding as if these permissions can;t be changed. maybe, 'system' VS 'custom'?

I must admit, I am not happy with any of the 3 options below. but maybe we can use them as a start for making this really UX friendly.

vijaycs85’s picture

Issue summary: View changes
FileSize
52.75 KB
46.76 KB
52.91 KB
60.54 KB

Seems like I didn't explain the page proper. here is another try...

alexrayu’s picture

Thanks for clarifying vijaycs85. Probably, the approach needs to be at least two-fold:

  1. Make the control items corresponding.
  2. Mark the locked items as such.

Given we want to call them 'locked'. When I first saw the 'locked' user roles, I thought I was going mad trying to understand, what had I done to 'lock' them and how to unlock :D Would it make sense to call them 'system' vs 'custom'? I think 'locked' and 'unlocked' is also fine, if we indicate it well. This is where those designs I posted come it. We can do it with text, with color, with icon (opening a small explanation popup), a combination of these.

alexrayu’s picture

FileSize
1.1 KB
1.04 KB

alexrayu’s picture

Vijay, Please see this patch for the Roles list. Don't look at the style yet - its very rough. Just want to see if I understood you correctly.

There are a few things that are concerning here, especially the element wights.

vijaycs85’s picture

Status: Active » Needs review

thanks for the patch @alexrayu. it looks great.

There are a few things that are concerning here, especially the element wights.

yeah, I was wondering why we need weight for roles. we can check with @moshe_work or @davidstrauss (user module maintainers) if there a use case. otherwise, we can get ride of them. for this patch point of view what we have in screenshot looks good.

However, we need to unify this UI approach for other pages as well. Not sure if this something we can easily get done by views?

Status: Needs review » Needs work

The last submitted patch, 6: 2280055-group-roles-by-origin-6.patch, failed testing.

alexrayu’s picture

The tests are failing because they will need to be changed if they are to go along this patch. However, I never really intended this patch for review. I don't really like what it does. The weights are ending up in different tables, which is plain wrong. I included this patch to start a conversation on what needs to be done and how.

alexrayu’s picture

Status: Needs work » Needs review
FileSize
3.12 KB
20.81 KB

Ok, here's a simple patch that does it without messing the row weights.

Status: Needs review » Needs work

The last submitted patch, 10: 2280055-unify-locked-unlocked-user-roles-10.patch, failed testing.

Bojhan’s picture

Issue tags: -D8UX usability +Usability

So I am not really sure about this, we are trying to resolve a problem that is very widespread and solved in multiple ways. And the interesting part is that it rarely comes up in any user testing we have done so far. So I am not even sure if it is a significant problem for users.

I'd be keen on taking a step back and looking at all of the parts this touches and actually validate whether the solution works. If we do it wrong, we might end up making loads of interfaces hard to understand. The whole two table approach is far from ideal.

alexrayu’s picture

@Bojhan: From what I understood, our ideas, including two tables, will need to rest until better times, if what we need to do is to bring interface to accord with #2119903: Show locked date formats in the UI. In that case, we have a single table, but have (locked) text appended to the labels of locked elements.

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

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should 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.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should 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.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should 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.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should 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.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should 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.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should 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.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.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: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should 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: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

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

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

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should 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.

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

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.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.5.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.