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 |
|---|---|
| 2015 | * } |
| 2016 | * @param array $args { |
| 2017 | * The args passed into `wp_update_custom_css_post()` merged with defaults. |
| 2018 | * |
| 2019 | * @type string $css The original CSS passed in to be updated. |
| 2020 | * @type string $preprocessed The original preprocessed CSS passed in to be updated. |
| 2021 | * @type string $stylesheet The stylesheet (theme) being updated. |
| 2022 | * } |
| 2023 | */ |
| 2024 | $data = apply_filters( 'update_custom_css_data', $data, array_merge( $args, compact( 'css' ) ) ); |
| 2025 | |
| 2026 | $post_data = array( |
| 2027 | 'post_title' => $args['stylesheet'], |
| 2028 | 'post_name' => sanitize_title( $args['stylesheet'] ), |
| 2029 | 'post_type' => 'custom_css', |
| 2030 | 'post_status' => 'publish', |
| 2031 | 'post_content' => $data['css'], |
| 2032 | 'post_content_filtered' => $data['preprocessed'], |
| 2033 | ); |