[MGNLMIGRATION-291] Dialog migration task does not convert correctly static fields Created: 09/Jan/14 Updated: 05/Feb/14 Resolved: 21/Jan/14 |
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | Migration Task |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Description |
|
Static fields in 4.5.x are read-only text fields which displays data coming from the JCR. They are migrated to the StaticFieldDefinition which in 5.x is a static text defines in the dialog definition. The correct target is a TextFieldDefinition with readOnly property set to false |
| Comments |
| Comment by Magnolia International [ 21/Jan/14 ] |
|
client was using static fields for some object managed by the data module. According to the client it worked like if it was readonly text field. I'am suspecting a custom field somewhere overriding the static definition. But no way to validate this hypothesis. |