Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-23180

async publishing can leave multiple versions in published state

    XMLWordPrintable

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: High High
    • None
    • 4.7.0
    • None
    • None

    Description

      How to reproduce:

      >> - set up 20 languages
      >> - activate async publication, do not start the daemon
      >> - create a content, e.g. a folder
      >> - create a draft of it in 13 languages (more than 10), do not publish them
      >> - click on "publish" on 3 or 4 drafts
      >> - start async daemon
      >> - click "publish" on all other drafts
      >> - check that current version has 13 languages
      >> - check the version history
      >>
      >> =>
      >>
      >> 3 versions are listed as published!
      >>
      >> PS: I tested the same behaviour, but with less open versions than the limit (ie. opening 4 drafts in 4 languages, click "publish" on 2, start async daemon, click publish on the other 2), and I still manage to get multiple versions in "published" state
      >
      > ...and I reproduced it even without stopping async publication
      > 1. create content with 14 translations
      > 2. in the tab listing the translations, ctrl click on the edit button to open 14 drafts in 14 browser tabs
      > 3. put mouse button above "publish button"
      > 4. in quick sequence, hit "click" + ctrl-tab to go to next browser tab, and keep publishing all 14 versions as fast as you can
      > 5. you end up with 3 or 4 published versions
      >

      without async publication, I could not manage to reproduce this. I tried my best to publish in parallel both untouched-drafts and previously-saved drafts (nb: all from one user account), and still I managed to get all my versions in a proper state, and without loosing changes

      Attachments

        Activity

          People

            Unassigned Unassigned
            gaetano.giunta-obsolete@ez.no Gaetano Giunta (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: