If you save a CPS changeset but don't actually change the CPS status, under certain circumstances it's possible for a record to be entered in the {cps_changeset_history} table anyway. Then when you go to the status page for the changeset and look at the site version history table, you see two entries in a row for the same transition, which doesn't make sense since the changeset only actually transitioned once.

CommentFileSizeAuthor
#1 cps-changeset-status-2476725-1.patch710 bytesDavid_Rothstein
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

David_Rothstein’s picture

David_Rothstein CreditAttribution: David_Rothstein at Tag1 Consulting commented
Status: Active » Needs review
FileSize
cps-changeset-status-2476725-1.patch710 bytes

Here is a patch that makes sure that can't happen.

merlinofchaos’s picture

merlinofchaos CreditAttribution: merlinofchaos commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

Status: Closed (fixed) » Needs work

The last submitted patch, 1: cps-changeset-status-2476725-1.patch, failed testing.

David_Rothstein’s picture

David_Rothstein CreditAttribution: David_Rothstein as a volunteer commented
Status: Needs work » Closed (fixed)

Testbot weirdness.