[MAGNOLIA-2687] Structural nodes in dialog definitions can't have nodedatas Created: 08/Apr/09  Updated: 02/Dec/13  Resolved: 02/Dec/13

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 4.0.1
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Marcel van den Brink Assignee: Philipp Bärfuss
Resolution: Outdated Votes: 0
Labels: admininterface, definition, dialog, nodedata
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File dialog_500.png     PNG File dialog_ok.png    
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   

We add some extra node data to our template, paragraph and dialog definitions in order to know which version is present on an instance.

This is done in the templating module. For a project a new folder is created. This makes it easier to import and export between developers. The folder contains all definitions plus a node data node called 'version'. This works great for the templates and paragraphs, but when we add it to the dialog definition it results in an HTTP 500 when requesting any dialog.

I added some screenshots of the admin interface when the dialogs work (dialog_ok.png) and don't work anymore (dialog_500.png).

According to a colleague it used to work in earlier versions of Magnolia, but in 4.01 it gives the error.



 Comments   
Comment by Philipp Bärfuss [ 15/Apr/09 ]

Since magnolia 4.0 any node (in dialogs section) which contains a nodedata is considered being a dialog.

Generated at Mon Feb 12 03:39:07 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.