Uploaded image for project: 'Alfresco'
  1. Alfresco
  2. ALF-734

Data loss: modifying the author field of a versioned document, then checking it out and back in again loses the value of the author field

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1 Enterprise
    • Fix Version/s: 3.4 Enterprise
    • Component/s: Repository
    • Labels:
      None
    • Environment:
      n/a
    • Resolution Time Custom Field:
      53 weeks, 1 day, 13 hours, 46 seconds

      Description

      Steps to reproduce:
      1. login to the Explorer UI
      2. upload a new file (leave the "author" field blank)
      3. turn on versioning (this step may not be relevant, but is left here as that's how this issue was reproduced - see ETHREEOH-3173)
      4. edit the metadata
      5. populate the "author" field
      6. confirm that the value of the author field was persisted
      7. checkout the file
      8. view the properties on the checked out version

      Expected result:

      • the author field is populated as per step #4

      Actual result:

      • the author field is blank

      Further steps:
      9. checkin the file
      10. view the properties on the original version

      Expected result:

      • the author field is populated as per step #4

      Actual result:

      • the author field is blank <- DATA LOSS!

      Note: this issue may be specific to the "author" field and/or the type of the file that's uploaded - I didn't seem to be able to reproduce the problem with the "description" field for an XLS document, but was able to with ACP and TXT files. Perhaps metadata extraction is related to this or something? The issue was common for the "author" field in all three files however, so that may be the best place to start.

      Also, the above process causes the JSF UI to get stuck in a property page loop of some kind - hitting close takes you back to the properties page again. I thought I'd corrupted my session but was able to reproduce it in another browser. Not sure exactly what steps cause this, but if you follow the above steps it happens consistently.

        Attachments

          Activity

            People

            • Assignee:
              closedbugs Closed Bugs
              Reporter:
              pmonks Peter Monks [X] (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Date of First Response: