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 |
---|---|
295 | * Whether to filter imported data through kses on import. |
296 | * |
297 | * Multisite uses this hook to filter all data through kses by default, |
298 | * as a super administrator may be assisting an untrusted user. |
299 | * |
300 | * @since 3.1.0 |
301 | * |
302 | * @param bool $force Whether to force data to be filtered through kses. Default false. |
303 | */ |
304 | if ( apply_filters( 'force_filtered_html_on_import', false ) ) { |
305 | kses_init_filters(); // Always filter imported data with kses on multisite. |
306 | } |
307 |
|
308 | call_user_func($wp_importers[$importer][2]); |
309 |
|
310 | include(ABSPATH . 'wp-admin/admin-footer.php'); |
311 |
|
312 | // Make sure rules are flushed |
313 | flush_rewrite_rules(false); |