[MGNLDAM-427] Upload button from "ImageChooser" stores to wrong location Created: 28/Mar/14  Updated: 21/May/14  Resolved: 21/May/14

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

Type: Bug Priority: Critical
Reporter: Rainer Blumenthal Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: aperto, support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File screenshot-1.jpg     JPEG File screenshot-2.jpg     JPEG File screenshot-3.jpg     JPEG File screenshot-4.jpg     JPEG File screenshot-5.jpg    
Issue Links:
Cloners
is cloned by MGNLDAM-446 CLONE - Upload button from "ImageChoo... Closed
Relates
dependency
depends upon MGNLUI-2893 Introduce getter for workbench root p... 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:
Visible to:
Frank Sommer, Oliver Emke

 Description   

We have separated the DAM into twi sections: /assets and /media-center ... if you use the Upload button in the bottom left corner of an image chooser, to upload an image during creating a text + image paragraph, the image is stored to the root folder instead of /assets.

If you configure an ImageChooser like in the screen attached: We expect the image to be stored under "/demo-features" but it ends up on root level.

For us this means an image is stored in nirvana, because editors only get access to sub-levels.

If you click on any folder in the chooser and than use the Upload button it works fine.



 Comments   
Comment by Eric Hechinger [ 28/Mar/14 ]

Behavior reproducible for a new component (like text image).
In case of existing component, we don't have this issue, and the upload field act as expected (uploaded image stored under the configured path)

Comment by Milan Divilek [ 15/May/14 ]

Patch can not be ported to DAM 2.0 version, because of changes done in MGNLUI-2761. Cloned ticket for fix in DAM 2.0 (MGNLDAM-446).

Comment by Christopher Zimmermann [ 21/May/14 ]

Reproduced on 5.2.5 EE bundle from today.

  • Configured Assets Workbench as screenshot.
  • confirmed that Assets app only showed demo-features contents.
  • Page editor / about/subsection-articles/article
  • Edit first content (Text Image)
  • Choose Image, "Select new..."
  • Deselect the selected asset.
  • Upload asset... it goes to root instead of "demo-features".
Comment by Milan Divilek [ 21/May/14 ]

Problem is not in this issue, but probably in MGNLUI-2111.

Choose Image, "Select new..."

Wrong workbench is resolved for "Choose dialog". You should see only demo-features content (as shown on screenshot-3), but instead content from whole repository is visible.

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