[wp-trac] [WordPress Trac] #38624: Allow starter content to apply after a site has already been set up and is no longer “fresh”

[WordPress Trac]

#38624: Allow starter content to apply after a site has already been set up and is
no longer “fresh”
-------------------------+-----------------------------
 Reporter:  westonruter  |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Future Release
Component:  Customize    |     Version:
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+-----------------------------

Comment (by webmandesign):

 Hi,

 Just adding additional info about the current implementation issue here:

 With current [https://github.com/WordPress/WordPress/blob/4.7/wp-includes
 /class-wp-customize-manager.php#L531 checking for `fresh_site`] it is
 actually [https://make.wordpress.org/core/2016/11/30/starter-content-for-
 themes-in-4-7/#comment-31762 not possible to use a theme starter content
 with WordPress network (multisite)] setup either. As `fresh_site` is
 actually set during the WordPress installation only and is nulled after
 publishing a post/page or saving a widget or customizer settings, which
 could already be triggered on one of sites in the network installation.

 Please keep this in mind too. Would be great if the feature works with
 WordPress network.

 Thanks and regards,

 Oliver

--
Ticket URL: <https://core.trac.wordpress.org/ticket/38624#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform