Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

*** The wcm.io Project is closing down this JIRA Instance in favor of GitHub issues. *** Please use the corresponding GitHub projects to report issues - or the mailing list for general discussion.

Drop Target Area definition in DamMediaSource should provide more control for activation and deactivation on the component level

Description

Currently the DamMediaSource enables drop area on components containing media elements, like images. in some cases, when a component contains subcomponents with media elements it causes problems when dropping a media element from the content finder on the first subcomponent. The image data is not posted to the subcomponent resource, but to the parent component, overriding the resource type, which makes the component unusable

it would be helpful, if the media handling would provide some control options over the drop area definition.

Gliffy Diagrams

Activity

Show:

Stefan Seifert December 1, 2014 at 5:09 PM

master ad4046

implement a first solution - please review/test

MediaArgs provides a new property "dragDropSupport" which gives more control, default ist "AUTO" which compares the current resource path with the resource for which the media handling is applied.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Priority

Created November 28, 2014 at 2:24 PM
Updated May 22, 2015 at 11:08 PM
Resolved December 1, 2014 at 5:09 PM
Configure