WP_Customize_Manager::customize_preview_init()

Hooks fired · 1

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

1. 1
   do_action( customize_preview_init )actionline 1960 (+54 into the body)

   Fires once the Customizer preview has initialized and JavaScript settings have been printed.

Uses · 10

• nocache_headers()Sets the HTTP headers to prevent caching for the different browsers.
• add_filter()Adds a callback function to a filter hook.
• current_user_can()Returns whether the current user has the specified capability.
• __()Retrieves the translation of $text.
• wp_enqueue_script()Enqueues a script.
• wp_enqueue_style()Enqueues a CSS stylesheet.
• add_action()Adds a callback function to an action hook.
• do_action()Calls the callback functions that have been added to an action hook.
• WP_Customize_Manager::wp_die()Custom wp_die wrapper. Returns either the standard message for UI or the Ajax message.
• WP_Customize_Manager::prepare_controls()Prepares panels, sections, and controls.

Used by · 1

• WP_Customize_Manager::wp_loaded()Registers styles/scripts and initialize the preview of each setting

Source

View on Trac ↗View on GitHub ↗

1906	public function customize_preview_init() {1907 1908		/*1909		 * Now that Customizer previews are loaded into iframes via GET requests1910		 * and natural URLs with transaction UUIDs added, we need to ensure that1911		 * the responses are never cached by proxies. In practice, this will not1912		 * be needed if the user is logged-in anyway. But if anonymous access is1913		 * allowed then the auth cookies would not be sent and WordPress would1914		 * not send no-cache headers by default.1915		 */1916		if ( ! headers_sent() ) {1917			nocache_headers();1918			header( 'X-Robots: noindex, nofollow, noarchive' );1919			header( 'X-Robots-Tag: noindex, nofollow, noarchive' );1920		}1921		add_filter( 'wp_robots', 'wp_robots_no_robots' );1922		add_filter( 'wp_headers', array( $this, 'filter_iframe_security_headers' ) );1923 1924		/*1925		 * If preview is being served inside the customizer preview iframe, and1926		 * if the user doesn't have customize capability, then it is assumed1927		 * that the user's session has expired and they need to re-authenticate.1928		 */1929		if ( $this->messenger_channel && ! current_user_can( 'customize' ) ) {1930			$this->wp_die(1931				-1,1932				sprintf(1933					/* translators: %s: customize_messenger_channel */1934					__( 'Unauthorized. You may remove the %s param to preview as frontend.' ),1935					'<code>customize_messenger_channel<code>'1936				)1937			);1938			return;1939		}1940 1941		$this->prepare_controls();1942 1943		add_filter( 'wp_redirect', array( $this, 'add_state_query_params' ) );1944 1945		wp_enqueue_script( 'customize-preview' );1946		wp_enqueue_style( 'customize-preview' );1947		add_action( 'wp_head', array( $this, 'customize_preview_loading_style' ) );1948		add_action( 'wp_head', array( $this, 'remove_frameless_preview_messenger_channel' ) );1949		add_action( 'wp_footer', array( $this, 'customize_preview_settings' ), 20 );1950		add_filter( 'get_edit_post_link', '__return_empty_string' );1951 1952		/**1953		 * Fires once the Customizer preview has initialized and JavaScript1954		 * settings have been printed.1955		 *1956		 * @since 3.4.01957		 *1958		 * @param WP_Customize_Manager $manager WP_Customize_Manager instance.1959		 */1960		do_action( 'customize_preview_init', $this );1961	}

History

Introduced in 3.4.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.8.8 tag, from src/wp-includes/class-wp-customize-manager.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.