[MAGNOLIA-4477] Migration module uses control 'editMode' which does not exist Created: 17/Jul/12  Updated: 10/Mar/21  Resolved: 10/Mar/21

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: 4.5.3
Fix Version/s: 4.5.x

Type: Bug Priority: Neutral
Reporter: Edgar Vonk Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLRES-6 Move CodeDialogEdit to the main codebase 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

 Description   

The [Magnolia 4.5 migration module|http://wiki.magnolia-cms.com/display/DEV/Using+the+Migration+module[ is broken I think.

It uses the 'editMode' control but this control does not exist anymore in Magnolia 4.5.3? I think it has been renamed to 'edit'.

When I open one of the Groovy scripts I get the error:

java.lang.RuntimeException: java.lang.IllegalArgumentException: Unknown control type: "editCode"

Workaround: make a copy of the 'edit' control and name it 'editCode' and it works again.

PS: are we the first ones to perform the upgrade using Magnolia 4.5.3?



 Comments   
Comment by Edgar Vonk [ 17/Jul/12 ]

Hmm, the 'edit' control does seem to be different than the old 'editCode'. The source code of the scripts is now on 1 line which causes the scripts to fail (because of missing eol's I think).

Or am I maybe just missing some module which contains the editCode control? I don't think I do.

Comment by Edgar Vonk [ 17/Jul/12 ]

Is MAGNOLIA-4468 related?

Comment by Edgar Vonk [ 17/Jul/12 ]

Extra information: when I deploy my web app on an empty installation the editCode control is there. Apparently it is a new control introduced in some version of the adminInterface module. It has the class: info.magnolia.cms.gui.dialog.DialogEditCode

I think the issue is that this control is not added during an upgrade of the adminInterface module? If this is true the problem lies in the version handler of the adminInterface.

Still: everyone who comes from an older Magnolia version will run into this issue I think.

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