As a system administrator, I can migrate my custom types from the data module to content apps
(MGNLDATA-201)
|
|
| Status: | Closed |
| Project: | Magnolia Data Module (closed) |
| Component/s: | None |
| Affects Version/s: | 2.2 |
| Fix Version/s: | 2.2 |
| Type: | Sub-task | Priority: | Major |
| Reporter: | Mikaël Geljić | Assignee: | Mikaël Geljić |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | workbench | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Date of First Response: | |
| Sprint: | 5.2-rc2 |
| Description |
|
Even after saving changes on a data item, the moddate column is always empty |
| Comments |
| Comment by Daniel Lipp [ 31/Oct/13 ] |
|
Maybe because the mgnl:lastModified mixin is missing? |
| Comment by Mikaël Geljić [ 31/Oct/13 ] |
|
Ok for just after migration, but shouldn't it be added when saving changes then? Besides, I don't have the warning when it sets mixin properties although the node is not of this mixin type. |
| Comment by Mikaël Geljić [ 01/Nov/13 ] |
|
Ok first thing was that the CreateDataAppTask didn't set the "propertyName" property to "mgnl:lastModified" on the moddate column. |
| Comment by Eric Hechinger [ 06/Nov/13 ] |
|
CreateDataAppTask use NodeTypes const instead of literal mgnl:lastModified |
| Comment by Mikaël Geljić [ 06/Nov/13 ] |
|
already using NodeTypes.LastModified.NAME in latest code |