[wp-trac] [WordPress Trac] #28605: Introduce customize capability for accessing Customizer
WordPress Trac
noreply at wordpress.org
Sat Jun 21 16:26:36 UTC 2014
#28605: Introduce customize capability for accessing Customizer
-----------------------------------+------------------------------
Reporter: westonruter | Owner:
Type: feature request | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Customize | Version: 3.4
Severity: normal | Resolution:
Keywords: has-patch 2nd-opinion | Focuses:
-----------------------------------+------------------------------
Comment (by celloexpressions):
Replying to [comment:2 engelen]:
> I agree that there should be a capability for accessing the theme
customizer, but I don't agree on the naming you propose. In my opinion,
`customize_theme` would be better-suited for this. With `customize`, it's
unclear what's being targeted, it could be anything. One could argue that
naming it `access_theme_customizer`, `use_theme_customizer` or even
`theme_customizer` would be even better, as it implies even more that it's
about the theme customizer and not just about "customizing" a theme (which
could mean anything).
One of the purposes behind having something other than
`edit_theme_options` for the customizer is to avoid making the assumption
that everything in the customizer is theme-related. While that is largely
the case now in core, several plugins introduce customizer controls that
are not theme-related, and some of these may be brought into core in the
future. `customize` would allow access to the Customizer itself, but
individual sections and controls would still have distinct capabilities
assigned to them for granular control over access.
Basically, we'd like to shift away from the term `Theme Customizer` and
toward just `Customizer` for the thing and `Customize` for the action.
Even now, anything that's stored as an `option` rather than a `theme_mod`
has implications beyond the current theme, and plugins should consider
using the customizer in place of custom settings pages if their options
are mostly visual.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/28605#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list