The problem was a specific CMIS server that was not able to send informations for getContentStreamFileName() and the fix was to use getContentStream().getFileName()
Pierre Gros (Inactive)
added a comment - The problem was a specific CMIS server that was not able to send informations for getContentStreamFileName() and the fix was to use getContentStream().getFileName()
The real problem is not in HTML Expert, it is in agent-main view and in some zone items in which agent photo should be displayed.
David Cartier-Michaud
added a comment - The real problem is not in HTML Expert, it is in agent-main view and in some zone items in which agent photo should be displayed.
But an url starting in cmis-root-collection:// is not surprising.
This difference in format is most likely due to being an Alfresco CMIS (that I have in local for testing), so it should be normal to have this difference in format from another type of CMIS.
Grégory Lefebvre (Inactive)
added a comment - - edited I am unable to reproduce the problem, I don't have any problem inserting an image from a CMIS, as an url in a HTML expert of a content.
However, I do notice a slight difference in the url format. I have :
${type:explorer#url:cmis-root-collection://c1d888db-ac64-47ee-a909-30c132d57bc4/ workspace://SpacesStore/267839b2-f466-42c5-9a35-cb3e41281bb9;1.0 #download:false}
But an url starting in cmis-root-collection:// is not surprising.
This difference in format is most likely due to being an Alfresco CMIS (that I have in local for testing), so it should be normal to have this difference in format from another type of CMIS.
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}]
The problem was a specific CMIS server that was not able to send informations for getContentStreamFileName() and the fix was to use getContentStream().getFileName()