Uploaded image for project: 'Service Packs and Hot Fixes'
  1. Service Packs and Hot Fixes
  2. MNT-2471

Moving a secondary child node using a file protocol adapter (such as CIFS) moves the primary child node

    Details

    • Type: Service Pack Request
    • Status: Closed (View Workflow)
    • Resolution: Fixed
    • Affects Version/s: 3.3.1
    • Fix Version/s: 4.0.1
    • Component/s: Installer
    • Labels:
      None
    • Environment:
      Generic
      Support: Windows 7 X64, JDK 1.6.0_21, MySQL 5.1.49, Tomcat 6.0.26
    • Bug Priority:
      Category 2
    • ACT Numbers:

      21827

      Description

      [ Problem ]
      Moving a secondary child node using a file protocol adapter (such as CIFS) moves the primary child node

      [ Details ]
      using CIFS/WebDAV to move a secondary child node from one folder to another actually moves the primary node instead. The secondary child node in this case has been created using the JS method addNode().

      [ Steps for replication ]
      1. Install Alfresco and bootstrap
      2. Create four spaces under Company Home 'folder1', 'folder2', 'folder3' and 'Report'
      3. Upload a document to 'folder1'
      4. Go into Company Home -> Data Dictionary -> Scripts and upload the attached javascript file.
      5. Execute the script from Company Home - this will create the secondary child node in 'folder2'
      6. Browse to 'folder2' in CIFS and move the document to 'folder3'

      [ Expected result ]
      The secondary child node located in 'folder2' is moved to 'folder3'

      [ Actual result ]
      The primary node is moved from 'folder1' to 'folder3'

      [ Additional info ]
      Tested on 3.0.1 thru 3.3.1

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                closedbugs Closed Bugs
                Reporter:
                astrachan Alex Strachan
              • Votes:
                1 Vote for this issue
                Watchers:
                3 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 week, 2 days, 5 hours
                  1w 2d 5h