[wp-trac] [WordPress Trac] #31089: Add revisions of settings to the Customizer
WordPress Trac
noreply at wordpress.org
Wed Nov 2 17:30:58 UTC 2016
#31089: Add revisions of settings to the Customizer
-------------------------+-----------------------------
Reporter: westonruter | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone: Future Release
Component: Customize | Version:
Severity: normal | Resolution:
Keywords: | Focuses: javascript
-------------------------+-----------------------------
Old description:
> In #30937 the concept of a “Customizer Transaction” is introduced,
> wherein each Customizer session gets a transaction containing the
> settings that are modified and eventually saved (or not). The
> `wp_transaction` is a custom post type with the settings JSON stored in
> the `post_content`. Every time the Customizer is accessed, a new
> `wp_transaction` post is created with `post_status=draft` and then when
> saving it becomes `post_status=publish`. As such, this automatically
> becomes a revision history for all saved changes to the Customizer.
>
> With the work on Transactions, however, there is no UI for accessing
> these revisions. There is no way to see previous revisions, to revert a
> revision, to recall a revision to continue changes.
>
> I did do some work on a [https://wordpress.org/plugins/settings-
> revisions/ Settings Revisions] plugin for a potential UI, where a new
> Customizer section is added to load a previous revision and to provide
> the “commit message” for the new one (see [https://wordpress.org/plugins
> /settings-revisions/screenshots/ plugin screenshots]). However, this
> plugin was written before transactions.
>
> See also:
> #21666 (Customizer reset/undo/revert)
> #20692 (Handle unsaved changes in the customizer)
> #28721 (Scheduled changes for the customizer)
> #31088 (Post revisions in the customizer)
New description:
In #30937 the concept of a “Customizer Transaction” is introduced, wherein
each Customizer session gets a transaction containing the settings that
are modified and eventually saved (or not). The `wp_transaction` is a
custom post type with the settings JSON stored in the `post_content`.
Every time the Customizer is accessed, a new `wp_transaction` post is
created with `post_status=draft` and then when saving it becomes
`post_status=publish`. As such, this automatically becomes a revision
history for all saved changes to the Customizer.
With the work on Transactions, however, there is no UI for accessing these
revisions. There is no way to see previous revisions, to revert a
revision, to recall a revision to continue changes.
I did do some work on a [https://wordpress.org/plugins/settings-revisions/
Settings Revisions] plugin for a potential UI, where a new Customizer
section is added to load a previous revision and to provide the “commit
message” for the new one (see [https://wordpress.org/plugins/settings-
revisions/screenshots/ plugin screenshots]). However, this plugin was
written before transactions.
See also:
#21666 (Customizer reset/undo/revert)
#20692 (Handle unsaved changes in the customizer)
#28721 (Scheduled changes for the customizer)
#31088 (Post revisions in the customizer)
#38624 (Allow starter content to apply after a site has already been set
up and is no longer “fresh”)
--
Comment (by westonruter):
@folletto closely related to #38624 (Allow starter content to apply after
a site has already been set up and is no longer “fresh”)
--
Ticket URL: <https://core.trac.wordpress.org/ticket/31089#comment:15>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list