[MGNLDAM-423] Uploaded images cannot be downloaded via UI Created: 25/Mar/14  Updated: 16/Jul/14  Resolved: 20/May/14

Status: Closed
Project: Magnolia DAM Module
Component/s: DAM App
Affects Version/s: 1.2.3
Fix Version/s: 1.2.5

Type: Bug Priority: Major
Reporter: Richard Unger Assignee: Daniel Lipp
Resolution: Fixed Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

LFRZ


Attachments: PNG File 5.2.5.png     PNG File 5.3.png     PNG File actionBar_FreshInstall.png     PNG File actionBar_Updated.png     PNG File actionDefinition_FreshInstall.png     PNG File actionDefinition_Updated.png    
Issue Links:
dependency
depends upon MGNLUI-2882 Implement action for downloading bina... Closed
relation
is related to MGNLDAM-400 Add ability to download an asset Closed
is related to MGNLDAM-432 Rework actions in Assets app to accom... Closed
is related to MGNLDAM-469 Wrong 'download asset' action registr... Closed
is related to DOCU-519 Document action for downloading binaries Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

How can an editor download a previously uploaded image from the DAM app?

In magnolia 4.4 there was both the "static link" and the possibility to Download the DMS content via right-click in the tree.

Please add this function in Magnolia 5. Editors cannot be expected to "work out" the link with which they can access their original file.

(or have I missed something obvious?)



 Comments   
Comment by Daniel Lipp [ 13/May/14 ]

The approach using the DamManager looks like a little overhead. I'd rather try to do with a slimmer approach (as we just discussed).

Comment by Jaroslav Simak [ 13/May/14 ]

Note: I aligned version of main & ui in the pom.xml because i think we should keep them consistent + updated module descriptor to respected those versions.

Comment by Daniel Lipp [ 15/May/14 ]

Just realized that it's not yet ported to DAM 2.0

Comment by Eric Hechinger [ 20/May/14 ]

We have a different order of the new action between 5.2.5 and 5.3. See attached screen shot.

Comment by Andreas Weder [ 20/May/14 ]

For the reordering, some renaming and reassignment of icons see the linked issue MGNLDAM-432

Comment by Eric Hechinger [ 20/May/14 ]

Update from a 5.x to 5.3 do not work as expected.
See related screenshot

Comment by Daniel Lipp [ 20/May/14 ]

version handling should be fixed now

Generated at Mon Feb 12 04:59:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.