[MGNLUI-2538] ChooseDialogPresenterImpl throws NPE after upgrade from 5.0.4 to 5.2.1 Created: 27/Dec/13  Updated: 23/Jan/14  Resolved: 14/Jan/14

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.2.1
Fix Version/s: 5.2.2

Type: Bug Priority: Critical
Reporter: Daniel Lipp Assignee: Eric Hechinger
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File Screen Shot 2013-12-26 at 23.13.44.jpg    
Issue Links:
relation
is related to MGNLACTIVATION-75 PathNotFoundException when upgrading ... Closed
is related to MGNLDAM-363 Publish incl. subnodes action is miss... Closed
is related to MGNLUI-2260 Missing config entry for WorkbenchFie... 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:
Epic Link: update_5.0.4_to_5.2.2

 Description   

After upgrading from 5.0.4 to 5.2.1, trying to use a LinkField results in NPE.

To reproduce:

  • take a 5.0.4 ce installation
  • upgrade to 5.2.1 ce
  • navigate to demo-project news-overview
  • press "select new"
    -> NPE


 Comments   
Comment by Daniel Lipp [ 06/Jan/14 ]

related with the two linked issues in the sense that all three appear after upgrade from 5.0.4 to 5.2.1

Comment by Eric Hechinger [ 06/Jan/14 ]
2014-01-06 08:41:47,632 ERROR magnolia.ui.form.field.factory.FieldFactoryFactory: No field type definition found for workbenchField
info.magnolia.registry.RegistrationException: Could not find fieldType for definition info.magnolia.ui.contentapp.field.WorkbenchFieldDefinition
	at info.magnolia.ui.form.fieldtype.registry.FieldTypeDefinitionRegistry.getByDefinition(FieldTypeDefinitionRegistry.java:88)
Comment by Daniel Lipp [ 10/Jan/14 ]

Caution: won't work whith a broken 5.2.1 installation. Fixes have to go into version handling of 5.2.2!

Generated at Mon Feb 12 08:57:40 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.