Customize: changeset_uuid query param doesn't get stripped at initial save of starter content
|Reported by:||westonruter||Owned by:||westonruter|
|Component:||Customize||Keywords:||has-patch commit dev-reviewed|
A changeset_uuid query parameter is added to the window's location via replaceState after a changeset is created and should remain until it is published. Upon publishing, the parameter should be removed because published changesets are frozen and cannot be opened in the customizer. When a changeset is published, a new changeset UUID is generated and is then supplied the next time changes are made.
When loading up a fresh_site and saving the starter content, the initial publishing is causing the next UUID to be supplied into changeset_uuid query param unexpectedly when it should be left empty.
Change History (8)
4 months ago
- Owner set to westonruter
- Resolution set to fixed
- Status changed from new to closed