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 |
---|---|
172 |
|
173 | // Render control templates. |
174 | $wp_customize->render_control_templates(); |
175 |
|
176 | /** |
177 | * Print Customizer control scripts in the footer. |
178 | * |
179 | * @since 3.4.0 |
180 | */ |
181 | do_action( 'customize_controls_print_footer_scripts' ); |
182 |
|
183 | /* |
184 | * If the frontend and the admin are served from the same domain, load the |
185 | * preview over ssl if the Customizer is being loaded over ssl. This avoids |
186 | * insecure content warnings. This is not attempted if the admin and frontend |
187 | * are on different domains to avoid the case where the frontend doesn't have |
188 | * ssl certs. Domain mapping plugins can allow other urls in these conditions |
189 | * using the customize_allowed_urls filter. |
190 | */ |