[MGNLRES-59] Adding binary resources through the admininterface doesn't work properly Created: 14/May/13  Updated: 29/Mar/22  Resolved: 16/May/13

Status: Closed
Project: Magnolia Resources Module
Component/s: None
Affects Version/s: 1.5.6
Fix Version/s: 1.5.7

Type: Bug Priority: Neutral
Reporter: Bence Vass Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLRES-54 IllegalStateException when trying to ... 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:
Team: Nucleus

 Description   

This problem occurs, when trying to add a binary resource to the resources workspace through the admininterface.

When a new item is created in the resource tree, "binary" is automatically selected as the resource type. But the following is missing from the metadata node: <sv:property sv:name="mgnl:template" sv:type="String"><sv:value>resources:binary</sv:value></sv:property>. It is only added when one resets the resource type, even though it is already preselected.

How to recreate the issue:

1. Click "new item" on a folder in the resources tree (f.e. templating-kit/themes/pop/img/bgs)
2. Edit the newly created "untitled" item
3. Choose any kind of binary resource from the filepicker and confirm (f.e. perms.png)
4. rename the item (f.e. perms)

5. double click on "resource type" to open the dropdown - choose binary again

The image is now available



 Comments   
Comment by Roman Kovařík [ 16/May/13 ]

Port to master not necessary - The issue MGNLRES-54 which causes this issue was not ported to master.

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