[BLOSSOM-192] Content Translation Support module throws NullPointerException when pages contain Blossom-Components Created: 16/Sep/14  Updated: 07/Nov/14  Resolved: 19/Sep/14

Status: Closed
Project: Blossom
Component/s: None
Affects Version/s: 3.0.2
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Adi De Masi Assignee: Tobias Mattsson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File BlossomAndSTKDialogBasedNodeDataToTranslateFinder.java     Text File BlossomDialogBasedNodeDataToTranslateFinder.java    
Issue Links:
causality
is causing MGNLCTS-63 Support for Blossom dialogs 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:

 Description   

When using the Export-Function of the Content Translation Support module, a NullPointerException occures if there is a blossom component on the page.

It is raised in the class info.magnolia.module.blossom.dialog.BlossomDialogDefinitionProvider

at Line 65/66:

DialogCreationContext context = DialogCreationContextHolder.get();
context.setId(dialogDescription.getId());

context is NULL here.



 Comments   
Comment by Tobias Mattsson [ 19/Sep/14 ]

Hi,

I have attached two classes that will fix this for you. Configure one of them at /modules/content-translation-support/config/nodeDataToTranslateFinder. Choose depending on whether you're using STK or not.

The reason this is needed is that Blossom supports making decisions in your code on whether to include fields or not. Based on the node being edited, the user logged in and so in. These things are what's in the context that is missing here. The attached classes will set up the context before attempting to access the dialog definition.

I have documented this on the wiki https://wiki.magnolia-cms.com/display/WIKI/Blossom+and+Content+Translation+Module

Comment by Tobias Mattsson [ 03/Oct/14 ]

UPDATE: The content translation support module will support Blossom dialogs out of the box as of version 2.0.2.

Generated at Sun Feb 11 23:31:03 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.