Opened 7 years ago
Closed 7 years ago
#42640 closed enhancement (invalid)
Setting general interface "New user default role"
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | |
Component: | Users | Keywords: | has-patch |
Focuses: | ui, accessibility, administration | Cc: |
Description
If anyone can register for the website, In admin interface of the general setting page the membership checkbox is checked then new user default role section should be displayed otherwise it should be hidden.
Attachments (2)
Change History (6)
#2
@
7 years ago
Doing it that way would force the user to first check the box, then save settings and reload the page for the dropdown to appear, so they can select a default role and hit "save changes" again.
These steps seem unnecessary and quite detrimental to the UX, some users may even miss the dropdown completely.
How about using JS instead to disable the dropdown when the box is unchecked, and enable it when checked?
(Just like the "Homepage" and "Post page" dropdowns in Settings > Reading are only enabled if you select the "static page" radio button above.)
This ticket was mentioned in Slack in #accessibility by afercia. View the logs.
7 years ago
#4
@
7 years ago
- Milestone Awaiting Review deleted
- Resolution set to invalid
- Status changed from new to closed
- Version 4.9 deleted
@harsh175 welcome to Trac and thanks for your proposal.
Discussed this ticket during today's accessibility meeting, and agreed it's not clear what the value added from hiding or disabling the default role "section" would be. There are a number of reasons why one would want to change the user default role even when "Anyone can register" is unchecked, for example during development.
Worth noting the default user role setting also affects the default selected role in the "Add new user" page (user-new.php
), so it is used also for other things, not strictly related to the "Anyone can register" checkbox.
There could also be other registration workflows etc. that could be impacted. For these reasons there was consensus to close this ticket, but please do feel free to reopen if something was missed. Conversation can continue also on closed tickets.
Attached screenshot for more clarification.