Uploaded image for project: 'Repository'
  1. Repository
  2. REPOSITORY-534

result of getAllRevisions is not in chronological order

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • 4.8.5, 4.9.0
    • 4.9.0
    • None
    • None
    • 4.9.0 M4
    • Oui

      A content that has been restored has JCR versions like :
      [1.0, 1.2, 1.3, 2.0, 2.1, 3.0]
      But the order of those revisions is not chronoligical.

      Current implementation of DefaultAmetysObject assume that this result is chronological and therefore is bogus.

          [REPOSITORY-534] result of getAllRevisions is not in chronological order

          Guillaume Gouin made changes -
          Fix Version/s New: 4.8.5 [ 19286 ]
          Guillaume Gouin made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          Bérénice Maurel made changes -
          Assignee New: Guillaume Gouin [ ggouin ]
          Status Original: Functional review OK [ 10207 ] New: In Progress [ 3 ]
          Magali Franchet made changes -
          Status Original: Available for review [ 10005 ] New: Functional review OK [ 10207 ]
          Guillaume Gouin made changes -
          Assignee Original: Guillaume Gouin [ ggouin ]
          Guillaume Gouin made changes -
          Status Original: In Progress [ 3 ] New: Available for review [ 10005 ]
          Guillaume Gouin made changes -
          Revue fonctionnelle renseignée New: Oui [ 10610 ]
          Guillaume Gouin made changes -
          Link New: This issue discovered while testing CMS-12276 [ CMS-12276 ]
          Guillaume Gouin made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Guillaume Gouin made changes -
          Rank New: Ranked higher
          Guillaume Gouin created issue -

            ggouin Guillaume Gouin
            ggouin Guillaume Gouin
            Guillaume Gouin Guillaume Gouin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: