[wp-trac] [WordPress Trac] #32772: Filter for disabling Customizer
WordPress Trac
noreply at wordpress.org
Wed Jul 1 14:04:41 UTC 2015
#32772: Filter for disabling Customizer
---------------------------+-----------------------------
Reporter: hereswhatidid | Owner:
Type: enhancement | Status: closed
Priority: normal | Milestone:
Component: Customize | Version: trunk
Severity: normal | Resolution: invalid
Keywords: | Focuses: administration
---------------------------+-----------------------------
Comment (by helen):
The comparison between the customizer and toolbar is interesting. The
toolbar's content is determined by various capabilities, and contains some
critical things like the log out link, which is why it can only be turned
off for the front end. In that way, its existence is not tied to a
capability of its own, so a filter makes sense. I wish we didn't have a UI
setting for turning it off per user, but I recall the passionate reaction
that led there.
The customizer similarly has its content determined by capabilities, but
is also in itself an editing tool. What I think is odd here, no matter the
method of turning it off, is that you end up with users who are empowered
to do X but not allowed to have a live preview mechanism for X. This is
probably okay when your users only use WP in a single context, but I think
today we're in a place where people are experiencing WP on more than one
site, and changing that availability, shifting contents and all, is a bit
of a disservice when it comes to the bigger picture. I'm not inherently
opposed to somebody not wanting to use the customizer on a personal level
- I certainly find it annoying in some workflows - but providing a filter
for this purpose is in essence endorsing disabling our current live
preview mechanism. That is not something I can globally get behind. Still
a wontfix for me, but better to document and discuss.
------
Replying to [comment:3 celloexpressions]:
> I have yet to see a valid reason for something like this.
> While you can remove the customize meta capability (or re-map it or
whatever), doing so simply because you don't want to train users or don't
want to use the Customizer is doing yourself and your users an enormous
disservice.
We are not omniscient, and even if your final opinion ends up being the
same, your process in getting there matters much more. By all means, think
this way if you must, but keep it to yourself if you can't also listen
without jumping to defense.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/32772#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list