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