[wp-trac] [WordPress Trac] #38114: Make it easier to visualize where to put your content in a given theme (aka "dummy content")
WordPress Trac
noreply at wordpress.org
Tue Nov 15 09:02:39 UTC 2016
#38114: Make it easier to visualize where to put your content in a given theme (aka
"dummy content")
----------------------------------------------------+---------------------
Reporter: helen | Owner: helen
Type: task (blessed) | Status: closed
Priority: normal | Milestone: 4.7
Component: Themes | Version:
Severity: normal | Resolution: fixed
Keywords: has-patch needs-testing needs-dev-note | Focuses:
----------------------------------------------------+---------------------
Comment (by westonruter):
In [changeset:"39241"]:
{{{
#!CommitTicketReference repository="" revision="39241"
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.
}}}
--
Ticket URL: <https://core.trac.wordpress.org/ticket/38114#comment:42>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list