[wp-trac] [WordPress Trac] #43122: customize.php fails to load with default changeset_uuid

[WordPress Trac]

#43122: customize.php fails to load with default changeset_uuid
--------------------------+-----------------------------
 Reporter:  bpayton       |      Owner:
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  Customize     |    Version:  4.9
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 I am seeing a rare condition where users are unable to load the Customizer
 with no specified changeset and see the message "Cheatin, uh? This
 changeset cannot be further modified."

 In all cases, I am seeing two `customize_changeset` posts with the same
 GUID post name, one with draft status and the other with published status.
 When WP_Customize_Manager attempts to find a changeset to load by default,
 it finds the draft with the GUID, and when it attempts to load the post,
 it finds the published post with the same GUID and dies with the message
 mentioned above.

 I read WP_Customizer and theorized how this could be happening but have no
 theory worth mentioning. Still, this seems like some kind of race
 condition.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/43122>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform