wp_update_custom_css_post( string $css, array $args = array() ): WP_Post|WP_Error

Description

Compatibility

Present in every tracked release (6.7.7 to 7.1.0), and compiles on PHP 7.4 through 8.6-dev.

Parameters

$cssstring

CSS, stored in post_content.

$argsarrayoptional

Args.Default: array()

• $preprocessedstring

  Optional. Pre-processed CSS, stored in post_content_filtered. Normally empty string.

• $stylesheetstring

  Optional. Stylesheet (child theme) to update. Defaults to active theme/stylesheet.

Return value

WP_Post|WP_Error

Post on success, error on failure.

Performance profile

How much work a call to wp_update_custom_css_post() does, and what it touches: the algorithmic scaling, the Zend instruction count per call across PHP versions, the hooks it hands control to, and the core code that calls it. Measured from the compiled opcodes, not a stopwatch, so every number is identical on any machine running the same PHP version, and every function in core is ranked by cost.

Cost class

Heavy

Reaches the database via get_post().

Scaling

Constant

No loop in the body: the same number of instructions runs whatever you pass in.

Instructions

67–93

Executed per call on PHP 8.5, depending on the branch taken. The body compiles to 106.

Plugin surface

1 hook

Third-party callbacks on 'update_custom_css_data' run inside this call, and their cost is not bounded by anything here.

Called by

1

1 place in core call this, so the cost is paid more often than your own code shows.

What it touches

• hookthird-party callbacksapply_filters()called directly
• querycontent queryget_post()called directly
• optionoption read or writeget_option()one call below wp_update_custom_css_post()

Further down the call graph this can also reach cache, serialize and transient. Those are the worst case, several calls deep and usually down an error path, not what a normal call pays.

What one call costs · 12 distinct outcomes

One number would be a lie: the work depends on which branch runs. These are every distinct cost wp_update_custom_css_post() can have, taken from its control-flow graph on PHP 8.5.

Hooks and filters fired · 1

One hook fires while wp_update_custom_css_post() runs, in this order:

1. 1
   apply_filters( update_custom_css_data )filterline 2134 (+49 into the body)

   Filters the `css` (`post_content`) and `preprocessed` (`post_content_filtered`) args for a `custom_css` post being updated.

Uses · 13

• wp_parse_args()Merges user defined arguments into defaults array.
• get_stylesheet()Retrieves name of the current stylesheet.
• apply_filters()Calls the callback functions that have been added to a filter hook.
• sanitize_title()Sanitizes a string into a slug, which can be used in URLs or HTML attributes.
• wp_get_custom_css_post()Fetches the `custom_css` post for a given theme.
• wp_update_post()Updates a post with new post data.
• wp_slash()Adds slashes to a string or recursively adds slashes to strings within an array.
• wp_insert_post()Inserts or update a post.
• is_wp_error()Checks whether the given variable is a WordPress Error.
• set_theme_mod()Updates theme modification value for the active theme.
• wp_get_latest_revision_id_and_total_count()Returns the latest revision ID and count of revisions for a post.
• wp_save_post_revision()Creates a revision for the current version of a post.

Used by · 1

• WP_Customize_Custom_CSS_Setting::update()Store the CSS setting value in the custom_css custom post type for the stylesheet.

Source code

View on Trac ↗View on GitHub ↗

2085function wp_update_custom_css_post( $css, $args = array() ) {2086	$args = wp_parse_args(2087		$args,2088		array(2089			'preprocessed' => '',2090			'stylesheet'   => get_stylesheet(),2091		)2092	);2093 2094	$data = array(2095		'css'          => $css,2096		'preprocessed' => $args['preprocessed'],2097	);2098 2099	/**2100	 * Filters the `css` (`post_content`) and `preprocessed` (`post_content_filtered`) args2101	 * for a `custom_css` post being updated.2102	 *2103	 * This filter can be used by plugin that offer CSS pre-processors, to store the original2104	 * pre-processed CSS in `post_content_filtered` and then store processed CSS in `post_content`.2105	 * When used in this way, the `post_content_filtered` should be supplied as the setting value2106	 * instead of `post_content` via a the `customize_value_custom_css` filter, for example:2107	 *2108	 * <code>2109	 * add_filter( 'customize_value_custom_css', function( $value, $setting ) {2110	 *     $post = wp_get_custom_css_post( $setting->stylesheet );2111	 *     if ( $post && ! empty( $post->post_content_filtered ) ) {2112	 *         $css = $post->post_content_filtered;2113	 *     }2114	 *     return $css;2115	 * }, 10, 2 );2116	 * </code>2117	 *2118	 * @since 4.7.02119	 * @param array $data {2120	 *     Custom CSS data.2121	 *2122	 *     @type string $css          CSS stored in `post_content`.2123	 *     @type string $preprocessed Pre-processed CSS stored in `post_content_filtered`.2124	 *                                Normally empty string.2125	 * }2126	 * @param array $args {2127	 *     The args passed into `wp_update_custom_css_post()` merged with defaults.2128	 *2129	 *     @type string $css          The original CSS passed in to be updated.2130	 *     @type string $preprocessed The original preprocessed CSS passed in to be updated.2131	 *     @type string $stylesheet   The stylesheet (theme) being updated.2132	 * }2133	 */2134	$data = apply_filters( 'update_custom_css_data', $data, array_merge( $args, compact( 'css' ) ) );2135 2136	$post_data = array(2137		'post_title'            => $args['stylesheet'],2138		'post_name'             => sanitize_title( $args['stylesheet'] ),2139		'post_type'             => 'custom_css',2140		'post_status'           => 'publish',2141		'post_content'          => $data['css'],2142		'post_content_filtered' => $data['preprocessed'],2143	);2144 2145	// Update post if it already exists, otherwise create a new one.2146	$post = wp_get_custom_css_post( $args['stylesheet'] );2147	if ( $post ) {2148		$post_data['ID'] = $post->ID;2149		$r               = wp_update_post( wp_slash( $post_data ), true );2150	} else {2151		$r = wp_insert_post( wp_slash( $post_data ), true );2152 2153		if ( ! is_wp_error( $r ) ) {2154			if ( get_stylesheet() === $args['stylesheet'] ) {2155				set_theme_mod( 'custom_css_post_id', $r );2156			}2157 2158			// Trigger creation of a revision. This should be removed once #30854 is resolved.2159			$revisions = wp_get_latest_revision_id_and_total_count( $r );2160			if ( ! is_wp_error( $revisions ) && 0 === $revisions['count'] ) {2161				wp_save_post_revision( $r );2162			}2163		}2164	}

Changelog

Introduced in 4.7.0. Unchanged from 6.7.7 through 7.1.0.

1. 6.7.7
2. 6.8.8
3. 6.9.7
4. 7.0.4
5. 7.1.0

Signature, return type and hooks compared across 5 parsed releases.

About this page

Parsed data

Generated from the wordpress-develop 6.9.7 tag, from src/wp-includes/theme.php, and regenerated for each WordPress release so it tracks the code rather than a snapshot of it.

Corrections

Something wrong on this page? Report it and it gets fixed in the next regeneration.