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

ezcontentstaging: syncing a copy fails if the copy is made from a version > 1

    Details

      Description

      any object with more than one version, if a copy is made, the copy cannot be synced.

      • create an object and edit to get at least to version 2
      • (optional) sync the object to bring both servers up to date.
      • make a copy of that object
      • sync the copy: the event fails

      the only exception is if the original object only has version 1. then the copy has version 1 too, and sync is successful.

        Issue Links

          Activity

          Hide
          Marcos Loureiro (Inactive) added a comment -

          QA Approved

          Show
          Marcos Loureiro (Inactive) added a comment - QA Approved
          Show
          Ricardo Correia (Inactive) added a comment - The following two documentation pages have been created: http://doc.ez.no/Extensions/eZ-Publish-extensions/eZ-Content-Staging/eZ-Content-Staging-1.x/Known-limitations http://doc.ez.no/eZ-Publish/User-manual/5.x/Content-Staging/Known-limitations
          Hide
          Marcos Loureiro (Inactive) added a comment -

          Related improvement created: EZP-21068

          Show
          Marcos Loureiro (Inactive) added a comment - Related improvement created: EZP-21068
          Hide
          Bertrand Dunogier added a comment -

          No end-user documentation should be required.

          Show
          Bertrand Dunogier added a comment - No end-user documentation should be required.
          Show
          Bertrand Dunogier added a comment - Merged to master: https://github.com/ezsystems/ezcontentstaging/commit/3e909ff4910723371fb3ff8d3fc3fb51fae28b45
          Hide
          Gaetano Giunta (Inactive) added a comment -

          @bd no, just one. Pbl is that obj gets created at version X > 1, and cs code thinks its not a new obj (create event) but an existing obj (edit event).
          See mail thread on sdk ml for extensive analysis of this

          Show
          Gaetano Giunta (Inactive) added a comment - @bd no, just one. Pbl is that obj gets created at version X > 1, and cs code thinks its not a new obj (create event) but an existing obj (edit event). See mail thread on sdk ml for extensive analysis of this
          Hide
          Bertrand Dunogier added a comment -

          Are there multiple entries for the same sync event (e.g. object published) in the queue ?

          Show
          Bertrand Dunogier added a comment - Are there multiple entries for the same sync event (e.g. object published) in the queue ?
          Hide
          Paulo Bras (Inactive) added a comment -

          another way to verify the problem:

          • Create a new object
          • Set in content.ini the DefaultVersionHistoryLimit to X (test value = 2)
          • Edit the new content more than X times (4)
          • Try to sync it:
              • The first 2 versions give you a serialization error (versions do not exist anymore)
              • The 3rd version exists but you have a 404 error

          base problem is the same, new object in target server is not being created with version 1.

          Show
          Paulo Bras (Inactive) added a comment - another way to verify the problem: Create a new object Set in content.ini the DefaultVersionHistoryLimit to X (test value = 2) Edit the new content more than X times (4) Try to sync it: The first 2 versions give you a serialization error (versions do not exist anymore) The 3rd version exists but you have a 404 error base problem is the same, new object in target server is not being created with version 1.

            People

            • Assignee:
              Unassigned
              Reporter:
              Paulo Bras (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Time Tracking

                Estimated:
                Original Estimate - 0 minutes
                0m
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 day, 5 hours, 36 minutes
                1d 5h 36m