Opened 10 years ago
Closed 10 years ago
#33488 closed defect (bug) (fixed)
_wp_customize_include() documentation
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 4.4 | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | Customize | Keywords: | needs-patch |
| Focuses: | docs | Cc: |
Description
Attachments (1)
Change History (12)
#2
@
10 years ago
- Owner set to wonderboymusic
- Resolution set to fixed
- Status changed from new to closed
#3
@
10 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
There are more scenarios where _wp_customize_include() runs, actually. In Widget Customizer, for instance, _wp_customize_include() sets up the WP_Customize_Manager for update-widget Ajax POST requests. It's also used in Menu Customizer partial refresh Ajax requests.
Basically the wp_customize=on request param is a signal for whether to bootstrap the Customizer when WordPress is loading. It's not necessarily tied to the preview frame.
This ticket was mentioned in Slack in #core by sergey. View the logs.
10 years ago
This ticket was mentioned in Slack in #core-customize by eric. View the logs.
10 years ago
Note: See
TracTickets for help on using
tickets.
In 33694: