[RESPDAM-37] Magnolia Dam Focal Areas is breaking the Assets-App in Magnolia 6.2.3 Created: 15/Sep/20  Updated: 14/Feb/22  Resolved: 17/Sep/20

Status: Closed
Project: DAM Focal
Component/s: None
Affects Version/s: 2.0
Fix Version/s: 2.0.1

Type: Bug Priority: High
Reporter: Daniel Brand Assignee: Adrien Manzoni
Resolution: Fixed Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Magnolia 6.2.3, Dam


Attachments: PNG File focalAreanodes.png     PNG File screenshot-1.png    
Issue Links:
relation
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:
Sprint: Sprint 7

 Description   

We recently upgraded from Magnolia 6.2.2 to Magnolia 6.2.3 which causes the break of the new Assets-App. When a new asset is uploaded the focalArea mgnl:contentNode is created but in addition since 6.2.3 there is a new node with an id and marked as type reference (see screenshot).

Error-Message:

java.lang.String cannot be cast to javax.jcr.Node. Stack trace: java.lang.ClassCastException: java.lang.String cannot be cast to javax.jcr.Nodejava.lang.String cannot be cast to javax.jcr.Node. Stack trace: java.lang.ClassCastException: java.lang.String cannot be cast to javax.jcr.Node at info.magnolia.dam.focal.area.field.FocalAreasFieldConverter.convertToPresentation(FocalAreasFieldConverter.java:43)

 

This causes the sub-app to crash, when we open an image because the module tries to load the contentNode but instead of the content node the reference not is used -> string ampping to a list.

Anothe issue is that the decorators are  breaking the app view. 
We have some custom fields like a damLinkField and we are also using the content tags module. This leads to not rendering the mentioned fields even if we provide them again in an decorator. After removing the dam focal module everything is working fine.

 

Also the UI of the Focal-Area tab isn't perfekt looking, huge pictures are using the whole screen.

 



 Comments   
Comment by Adrien Manzoni [ 17/Sep/20 ]

Hi dbrand

I will tackle the first part of the description in this ticket.

The second seems related to another CORE issue.

The 3rd one would deserve a dedicated ticket with a bit more detail (such as the screen resolution used, the image you tried to upload).

 

Regards

Adrien

Comment by Adrien Manzoni [ 17/Sep/20 ]

Released in 2.0.1

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