[ACE-4811] Copy Move action doesn't show the current path where the node is in Created: 24-Nov-15  Updated: 01-Sep-17

Status: Open
Project: Alfresco One Platform
Component/s: Document Library
Affects Version/s: Community Edition 201510 EA
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Tahir Malik Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Windows, PostgreSQL, Tomcat 7.

Attachments: PNG File Pasted image at 2015_11_24 04_33 PM.png    
ACT Numbers:


Regression Since:


In 4.2.e, the Move Dialog opens with the folder tree on the right expanded to show the location of the current file. This makes it much easier to move a document into a neighboring folder, as the user doesn't have to browse to find it.

In 5.1.c, the Move Dialog opens with the folder tree on the right only showing the top level of folders.

The dialogs otherwise look and behave identically.

The screenshot below shows this issue. In this case the node is 6 levels deep, but the picker only shows the first level in the site and the root node is selected.

Comment by David Draper [X] (Inactive) [ 05-Dec-15 ]

Richard Esplin [X] Did you see this in the copy/move dialogs in search or in the document library actions?

Comment by Tahir Malik [ 05-Dec-15 ]

I saw this is in the document library.

Comment by Richard Esplin [X] (Inactive) [ 08-Dec-15 ]

Like Tahir, I see it with both the move and copy actions from the document library page and the document details page.

It is easy to reproduce in a default install with the Sample: Web Design Project site. Just browse through the "Project Library" to any folder below the first tier.

Comment by David Draper [X] (Inactive) [ 08-Dec-15 ]

OK... but we can agree this has absolutely nothing to do with Aikau? This is most likely a change that got made in 5.0 (rather than 5.1) probably around the time it was being updated to include the "My files" and "Shared" root elements.

Comment by Tahir Malik [ 08-Dec-15 ]

Hi David,

I guess it has to do with Aikau . In 4.2. there were the old school actions --> copy-move-to.js.
After 5.0 the actions were re-written in Aikau -->* alfresco\services\actions\CopyMoveService.js*.

In the old action it was the variable: this.currentPath.
I guess in the CopyMoveService.js this.repoNodeRef isn't being picked up like it should be.

widgetsContent: [
                  name: "alfresco/pickers/ContainerPicker",
                  config: {
                     singleItemMode: singleItemMode,
                     generatePubSubScope: true,
                     repoNodeRef: this.repoNodeRef || "alfresco://company/home"
Comment by David Draper [X] (Inactive) [ 08-Dec-15 ]

Tahir Malik Richard Esplin [X] There is clearly some confusion here... the CopyMoveService isn't used in the Document Library (none of Aikau is). So I don't see what this has to do with Aikau?

The actions for the Document Library are still handled by the old code.... the actions for the faceted search page are handed by Aikau, because it's an Aikau page. Faceted search has only been present since 5.0, it is a brand new page and has not regressed anything from 4.2.

If the Document Library actions have changed, that's entire different - the point is about determining where the issue will be addressed and which team picks up the work and what code has to be worked on.

Comment by Richard Esplin [X] (Inactive) [ 08-Dec-15 ]

I changed the component to "Document Library", and rewrote the description to clearly describe what we know about the actual problem.

I removed the guesses at the underlying cause so that we can correctly triage the issue.

Thank you Tahir and David for helping us to understand the issue.

Generated at Sat Jul 11 06:20:58 BST 2020 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.