WP hooks navigation: Home/browse • Actions index • Filters index
To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).
The best way to understand what a hook does is to look at where it occurs in the source code.
do_action( "hook_name" )apply_filters( "hook_name", "what_to_filter" ).Remember, this hook may occur in more than one file. Moreover, the hook's context may change from version to version.
| Line | Code |
|---|---|
| 171 | $wp_customize->render_panel_templates(); |
| 172 | $wp_customize->render_section_templates(); |
| 173 | $wp_customize->render_control_templates(); |
| 174 | |
| 175 | /** |
| 176 | * Print Customizer control scripts in the footer. |
| 177 | * |
| 178 | * @since 3.4.0 |
| 179 | */ |
| 180 | do_action( 'customize_controls_print_footer_scripts' ); |
| 181 | |
| 182 | /* |
| 183 | * If the frontend and the admin are served from the same domain, load the |
| 184 | * preview over ssl if the Customizer is being loaded over ssl. This avoids |
| 185 | * insecure content warnings. This is not attempted if the admin and frontend |
| 186 | * are on different domains to avoid the case where the frontend doesn't have |
| 187 | * ssl certs. Domain mapping plugins can allow other urls in these conditions |
| 188 | * using the customize_allowed_urls filter. |
| 189 | */ |