This repository was archived by the owner on Dec 16, 2022. It is now read-only.
Fix saving of postmeta in scheduled changesets #375
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a scheduled changeset publishes via WP Cron, the Customizer will bootstrap after the
initaction. In the course of normal Customizer bootstrapping, it happens at theplugins_loadedaction. Because postmeta currently is registered at theinitaction, this means that the postmeta will not get registered during WP Cron because the Customizer will bootstrap afterinit.This is also a problem for changesets that get published via WP-CLI, since
initalso is done beforewp post update $changeset_post_id --post_status=publish.In the Customizer the way to reproduce the problem is: