[DOCU-780] Clarify usage of DAM upload field Created: 02/Aug/16  Updated: 03/Jul/17  Resolved: 02/Aug/16

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Richard Gange Assignee: Richard Gange
Resolution: Done Votes: 0
Labels: core
Remaining Estimate: 0d
Time Spent: 0.25h
Original Estimate: Not Specified

Issue Links:
relation

 Description   

We need to reconsider how we present the DAM upload field in our documentation. Already we have seen a lot of confusion about what it exactly does. It's name is misleading. Customers get the impression that this field can be configured anywhere and it will upload to the DAM. Not true. It's name comes from the fact that it was designed to be a field in the DAM detail subApp. Due to the documentation of this field customers have started using it in other places. We should make it clear in our documentation that the field does not upload the file to the DAM. It uploads the file according to how and where the field is being used. Just like any other field.



 Comments   
Comment by Tom Wespi [ 02/Aug/16 ]

We use this field very often because it is way simpler for the customer just to publish one item in an app and knowing everything is published. When linking to DAM the customer has to publish 2 items located in two apps.

Comment by Richard Gange [ 02/Aug/16 ]

Thanks Tom. The problem is the name. DAMUploadField. People think that means no matter where it's configured the image will go to the DAM. Perhaps we could create an AdvancedUploadField or something if editing images from a dialog is something we want to support.

Comment by Christoph Meier [ 02/Aug/16 ]

I completely agree in what rgange is saying - but i also see tomwespis point.

However - i was recommending the basic upload field for cases where you want the image on the same node (as your current content item or page), see https://documentation.magnolia-cms.com/display/DOCS/Working+with+images+using+imgfn

But since the dam upload field extends the basic one - it seems to have more possibilities (i have never used the dam upload field yet tbh).

Comment by Richard Gange [ 02/Aug/16 ]

I think what we need is a new field in ui-framework for advanced upload options. The DAM version could very well just extend that.

Comment by Richard Gange [ 02/Aug/16 ]

Added more clarification and a rewording to the intro. Also added a usage section the bottom.

If you are using this field outside the DAM please be aware of MGNLUI-3968. Both Basic and DAM upload fields have this issue.

Comment by Christoph Meier [ 02/Aug/16 ]

Thnx rgange - very nice edit.

Generated at Mon Feb 12 01:12:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.