Changeset 39241 for trunk/src/wp-includes/class-wp-customize-nav-menus.php

Timestamp:

11/15/2016 09:02:38 AM (10 years ago)

Author:

westonruter

Message:

Customize: Allow starter content to apply in a new theme when switching from another theme containing changes.

• Ensure that starter content can apply from theme B after previewing starter content in theme A.
• Introduce new starter_content flag in changeset setting params which is used to capture whether a value is starter content and thus can be overridden.
• Create changeset up-front with starter_content flags instead of waiting for AUTOSAVE_INTERVAL.
• Eliminate instantiation of settings for widget instances in favor of directly calling sanitize_widget_js_instance. This eliminates issues with looking for widgets before they are registered.
• Ensure that non-placeholders (inline arrays instead of string references) can be supplied in starter content.
• Re-use auto-draft posts as starter content across theme switches.
• Introduce starter_content param for WP_Customize_Manager::save_changeset_post() which is false except when starter content is being loaded on a fresh_site.

See #38114.
Fixes #38541.

File:

• trunk/src/wp-includes/class-wp-customize-nav-menus.php (modified) (1 diff)

trunk/src/wp-includes/class-wp-customize-nav-menus.php

@@ -697 +697 @@
                 $this->manager->add_setting( new WP_Customize_Filter_Setting( $this->manager, 'nav_menus_created_posts', array(
                         'transport' => 'postMessage',
+                        'type' => 'option', // To prevent theme prefix in changeset.
                         'default' => array(),
                         'sanitize_callback' => array( $this, 'sanitize_nav_menus_created_posts' ),