Won't fix right now.
We target files by id and not by path.
In your use case, the file has mor than one path, and some paths are not allowed for the user.
We do not cover such use cases.
Cédric Damioli
added a comment - Won't fix right now.
We target files by id and not by path.
In your use case, the file has mor than one path, and some paths are not allowed for the user.
We do not cover such use cases.
Hyp : A CMIS folder (from Alfresco) is set in Ametys resources explorer
In an Ametys content, a link is done (file to download) on a file from CMIS folder.
On Alfresco side, the parent folder of the file is renamed (the path changed in Alfresco) => The link to file is broken
David Cartier-Michaud
added a comment - Hyp : A CMIS folder (from Alfresco) is set in Ametys resources explorer
In an Ametys content, a link is done (file to download) on a file from CMIS folder.
On Alfresco side, the parent folder of the file is renamed (the path changed in Alfresco) => The link to file is broken
Can you please elaborate on the issue ? I don't understand the case you are describing. What file do you mean ? what folder ?
Guillaume Gouin
added a comment - Can you please elaborate on the issue ? I don't understand the case you are describing. What file do you mean ? what folder ?
Unassigned
David Cartier-Michaud
Votes:
0Vote for this issue
Watchers:
3Start watching this issue
Created:
Updated:
Resolved:
{"errorMessages":["jqlTooComplex"],"errors":{}}
[{"id":-1,"name":"My open issues","jql":"assignee = currentUser() AND resolution = Unresolved order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-2,"name":"Reported by me","jql":"reporter = currentUser() order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":true},{"id":-4,"name":"All issues","jql":"order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-5,"name":"Open issues","jql":"resolution = Unresolved order by priority DESC,updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-9,"name":"Done issues","jql":"statusCategory = Done order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-3,"name":"Viewed recently","jql":"issuekey in issueHistory() order by lastViewed DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-6,"name":"Created recently","jql":"created >= -1w order by created DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-7,"name":"Resolved recently","jql":"resolutiondate >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false},{"id":-8,"name":"Updated recently","jql":"updated >= -1w order by updated DESC","isSystem":true,"sharePermissions":[],"requiresLogin":false}]
Won't fix right now.
We target files by id and not by path.
In your use case, the file has mor than one path, and some paths are not allowed for the user.
We do not cover such use cases.