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 |
---|---|
331 | * Whether to filter imported data through kses on import. |
332 | * |
333 | * Multisite uses this hook to filter all data through kses by default, |
334 | * as a super administrator may be assisting an untrusted user. |
335 | * |
336 | * @since 3.1.0 |
337 | * |
338 | * @param bool $force Whether to force data to be filtered through kses. Default false. |
339 | */ |
340 | if ( apply_filters( 'force_filtered_html_on_import', false ) ) { |
341 | kses_init_filters(); // Always filter imported data with kses on multisite. |
342 | } |
343 |
|
344 | call_user_func( $wp_importers[ $importer ][2] ); |
345 |
|
346 | include( ABSPATH . 'wp-admin/admin-footer.php' ); |
347 |
|
348 | // Make sure rules are flushed |
349 | flush_rewrite_rules( false ); |