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 |
|---|---|
| 158 | </form> |
| 159 | <div id="customize-preview" class="wp-full-overlay-main"></div> |
| 160 | <?php |
| 161 | |
| 162 | /** |
| 163 | * Print Customizer control scripts in the footer. |
| 164 | * |
| 165 | * @since 3.4.0 |
| 166 | */ |
| 167 | do_action( 'customize_controls_print_footer_scripts' ); |
| 168 | |
| 169 | // If the frontend and the admin are served from the same domain, load the |
| 170 | // preview over ssl if the customizer is being loaded over ssl. This avoids |
| 171 | // insecure content warnings. This is not attempted if the admin and frontend |
| 172 | // are on different domains to avoid the case where the frontend doesn't have |
| 173 | // ssl certs. Domain mapping plugins can allow other urls in these conditions |
| 174 | // using the customize_allowed_urls filter. |
| 175 | |
| 176 | $allowed_urls = array( home_url('/') ); |