You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
URL of page:<siteurl>/admin/users?name=&rank_id=0&sort=alias or <siteurl>/admin/users?name=&rank_id=0&sort=alias-reverse Description of bug: Attempting to use 'Sort by Alias (A-Z)' or 'Sort by Alias (Z-A)' on the Admin version of the User Index shows results that do not match any sorting method. It seems similar to 'Oldest First' and 'Newest First' at first glance, but some user names do nto match up. How was the bug caused (exact steps to reproduce): Go to the Admin Home, go to the User Index from there, pick either 'Sort by Alias (A-Z)' or 'Sort by Alias (Z-A)' and click Search.
Further details
Unlike the public User Index, this one actually does something.. but it's unclear what. At first glance, I assumed it was matching with Oldest First (if sorting by A-Z) or Newest first (if sorting by Z-A), but on closer look didn't match even that.
The text was updated successfully, but these errors were encountered:
Bug as reported:
(Main branch, last commit parent: f447da64)
URL of page:
<siteurl>/admin/users?name=&rank_id=0&sort=alias
or<siteurl>/admin/users?name=&rank_id=0&sort=alias-reverse
Description of bug: Attempting to use 'Sort by Alias (A-Z)' or 'Sort by Alias (Z-A)' on the Admin version of the User Index shows results that do not match any sorting method. It seems similar to 'Oldest First' and 'Newest First' at first glance, but some user names do nto match up.
How was the bug caused (exact steps to reproduce): Go to the Admin Home, go to the User Index from there, pick either 'Sort by Alias (A-Z)' or 'Sort by Alias (Z-A)' and click Search.
Further details
Unlike the public User Index, this one actually does something.. but it's unclear what. At first glance, I assumed it was matching with Oldest First (if sorting by A-Z) or Newest first (if sorting by Z-A), but on closer look didn't match even that.
The text was updated successfully, but these errors were encountered: