WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #38541


Ignore:
Timestamp:
10/28/2016 04:33:32 AM (4 years ago)
Author:
westonruter
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #38541 – Description

    initial v1  
    1 See #38114. At the moment, starter content is only applied to the customized state if if there is no changeset ost existing for the current UUID. However, if I have a fresh site and I preview Twenty Seventeen and then, without activating, I do a theme switch to another theme that has starter content, I should see that theme's starter content merged on top of the previous starter content since the site is still fresh. A complication here is with the `auto-draft` post/page. The existence of the changeset provided a locking mechanism to prevent these posts from being created repeatedly in a given session. What needs to be done, however, is to ensure that they only get created once for a given theme's imported starter content.
     1See #38114. At the moment, starter content is only applied to the customized state if if there is no changeset post existing for the current UUID. However, if I have a fresh site and I preview Twenty Seventeen and then, without activating, I do a theme switch to another theme that has starter content, I should see that theme's starter content merged on top of the previous starter content since the site is still fresh. A complication here is with the `auto-draft` post/page. The existence of the changeset provided a locking mechanism to prevent these posts from being created repeatedly in a given session. What needs to be done, however, is to ensure that they only get created once for a given theme's imported starter content.