-
Notifications
You must be signed in to change notification settings - Fork 37
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
Dissallow hiding or removing the themes section of the customizer #127
Comments
See branch issue-127-removing-customizer-active-theme |
I've assigned this for a later release, since we are lacking decision on this. |
I'll vote for not allowing changing the themes section. |
I'd agree too that themes shouldn't remove the theme switcher functionality. In watching new users, I've seen a lot of people who use the switching functionality in the customizer as the "normal" way of switching their themes(and discovering new ones), and not rely so much on the dashboard. |
There doesn't really need to be any further discussion on this. This falls under the universal "Don't be a d***" guideline. I don't think there's anyone on the team that would be against having this in. |
On the other hand I have only seen this happen once. It might not be worth the effort. |
Perhaps a more general warning for |
Triage resolution: We should add this as a sniff. The handbook should also be updated (there are parts with |
The theme section in the customizer shows the name of the active theme and the Change button where the user can preview and select another theme.
By hiding or removing the section authors can lock users in.
Rule type:
Error
Rule:
[Optional Section] Decision needed:
We have allowed users to move and in some exceptions, remove existing sections, but I feel that this needs to be an exception.
Notes for implementation:
Examples:
To do:
The text was updated successfully, but these errors were encountered: