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

Content Staging: publish event not removed from feed if target server has 'Wait until date' workflow

    XMLWordPrintable

    Details

      Description

      With Content Staging, syncing a new content object to a target server/endpoint with a "Wait until date" workflow will cause the event to not be removed from the list (but the content still appears to be synced correctly).

      Steps to reproduce:

      1. On the target server/instance/etc setup a "Wait until date" workflow to trigger on content/before/publish, (i.e: Article->Publish Date)
      2. On the source server, with no workflows besides the ones used by Content Staging, create a new object (i.e Article)
      3. Go to the Content Staging feeds list and attempt to sync the content
      4. The sync event will fail with the following error:

      Object 73 to be synchronised to feed target_instance: failure (HTTP error 400 (Bad Request)) [Event 19]
      

      In var/log/error.log:

      [ ... ] [127.0.0.1] eZContentStagingEvent::syncEvents:
      Failed syncing event 19, transport error code: HTTP error 400 (Bad Request)
      

      5. Repeating the sync attempt, the action fails once more, but a different error is logged:

      [ ... ] [127.0.0.1] eZContentStagingEvent::syncEvents:
      Failed syncing event 19, transport error code: HTTP error 400 (Bad Request)
      [ ... ] [127.0.0.1] eZMySQLiDB:
      Query error (1062): Duplicate entry '31e74fdd3caddf5ea7bb820c68ea3513' for key 'ezcontentobject_remote_id'. Query: UPDATE ezcontentobject SET section_id=0, owner_id=14, contentclass_id=16, name='New Article',
          published=0, modified=0, current_version=1, status=0,
          remote_id='31e74fdd3caddf5ea7bb820c68ea3513', language_mask=2, initial_language_id=2 WHERE  id='66'
      [ ... ] [127.0.0.1] eZDBInterface::commit TRANSID-75210cd5b40a3863f6e5a26a18c33c4d:
      Transaction in progress failed due to DB error, transaction was rollbacked. Transaction ID is TRANSID-75210cd5b40a3863f6e5a26a18c33c4d.
      [ ... ] [127.0.0.1] eZContentStagingEvent::syncEvents:
      Failed syncing event 19, transport error code: HTTP error 400 (Bad Request)
      

      6. Checking the target server, the object can be seen in the "My pending items" list, and it will eventually be published correctly once its publishing date is reached, as expected.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                Filipe.Dobreira@ez.no Filipe Dobreira (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                8 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Time Spent - 2 days, 6 hours, 40 minutes Remaining Estimate - 45 minutes
                  45m
                  Logged:
                  Time Spent - 2 days, 6 hours, 40 minutes Remaining Estimate - 45 minutes
                  2d 6h 40m