Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

User roles are sorted inconsistently on user group update page #7315

Closed
gadamiak opened this issue Mar 6, 2012 · 1 comment
Closed

User roles are sorted inconsistently on user group update page #7315

gadamiak opened this issue Mar 6, 2012 · 1 comment
Labels
proposal Proposal about improvement aka RFC. Need to be discussed before start implementation. type-frontend Issues related to UI/UX issues, mostly about styles and frontend implementations on JavaScript.

Comments

@gadamiak
Copy link

gadamiak commented Mar 6, 2012

gadamiak created Redmine issue ID 7315

Access policies on 'update user group' page are sorted inconsistently:

  • on 'users' tab from highest (0) to lowest (9999); additionally they lack the authority number
  • on 'context access' tab from lowest (9999) to highest (0)
  • on 'resource group access' from highest (0) to lowest (9999)

Can't determine on other tabs. The sorting order should be from lowest (9999) to highest (0) IMO.

@splittingred
Copy link

splittingred submitted:

Fixed: 86b0be0

enigmatic-user pushed a commit to enigmatic-user/revolution that referenced this issue Feb 13, 2014
enigmatic-user pushed a commit to enigmatic-user/revolution that referenced this issue Feb 13, 2014
* release-2.2:
  Update to xPDO 2.2.3-pl
  Prevent fatal error if invalid class_key is passed to Resource edit/create page
  [modxcms#7052] Prevent username/host/dbname from being set as a system setting placeholder
  [modxcms#3860] Fix session issue with modUser joinGroup/leaveGroup methods
  [modxcms#7315] Standardize default sorting for User Group access grids
  Fix persistence issue with clear cache checkbox on resources without change state
  Fixed ellipsis filter to not cut off html tags in property
  [modxcms#7326] fix inability to unset a TV's Input Option Values field
  [modxcms#7306] Sanity check for reload data for resource groups when changing template of new resource
  [modxcms#7279] Handle edge case where processor classes might already be loaded with CRCs causing issues with runProcessor
  add dashboard name to dashb heading on non-default dashb
  [modxcms#3818] Add UI/processing to set response code for weblinks
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposal Proposal about improvement aka RFC. Need to be discussed before start implementation. type-frontend Issues related to UI/UX issues, mostly about styles and frontend implementations on JavaScript.
Projects
None yet
Development

No branches or pull requests

2 participants