Make WordPress Core

Opened 6 months ago

Last modified 2 hours ago

#38624 new enhancement

Allow starter content to apply after a site has already been set up and is no longer “fresh”

Reported by: westonruter Owned by:
Milestone: 4.8 Priority: normal
Severity: normal Version:
Component: Customize Keywords:
Focuses: Cc:


Starter content for themes was introduced in #38114. In order to prevent the starter content from overriding a site's existing content, a fresh_site option flag was added to prevent the content from applying after the site has been first updated. This means the starter content has limited use when installing new themes to try out during the life of a site.

The primary problem for applying starter content on an existing site is how to handle the merge conflicts, how to decide when to use the starter content/configs and when to use existing site content/configs. One option would be a button to “reset” a site to use the starter content. For more granularity, once the starter content is applied there could be a list of the settings that were modified so that you could then go through and evaluate each change to see if you want to keep it. Each control that has a setting containing dirty starter content could be highlighted in some way with a button that allows you to revert the starter content or toggle the starter content so you can compare before/after.

This is closely related to #21666 (Customizer reset/undo/revert) and #31089 (Add revisions of settings to the Customizer).

Change History (8)

#1 @westonruter
6 months ago

  • Type changed from defect (bug) to enhancement

This ticket was mentioned in Slack in #themereview by rabmalin. View the logs.

5 months ago

#3 @westonruter
5 months ago

I want there to be a feature plugin soon that provides a UI, a button, for applying starter content to your already-established site. I also want there to be a UI for being able to select from among multiple sets of starter content.

#4 @webmandesign
4 months ago


Just adding additional info about the current implementation issue here:

With current checking for `fresh_site` it is actually 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,


This ticket was mentioned in Slack in #core-customize by westonruter. View the logs.

3 months ago

#6 @westonruter
3 months ago

  • Milestone changed from Future Release to 4.8

This ticket was mentioned in Slack in #core-customize by westonruter. View the logs.

7 weeks ago

This ticket was mentioned in Slack in #themereview by suganya. View the logs.

2 hours ago

Note: See TracTickets for help on using tickets.