After you publish a changeset, sometimes you will see that on the initial page load after the publishing happens, the changeset is still presented on the screen as though it were unpublished.

I think this is more likely to happen on sites that have a lot of CPS content where the publishing process takes a while to finish.

It appears to be due to a race condition involving the database transaction that is used during publishing and the code that notifies the client that the changeset was published.

Comments

David_Rothstein created an issue. See original summary.

David_Rothstein’s picture

Status: Active » Needs review
StatusFileSize
new2.06 KB

Here is a patch. Fixes it for the "unpublish" situation too (just in case; in practice I haven't seen the bug there but in theory it could occur).

hadsie’s picture

Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

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