[MGNLMIGRATION-91] Resources repository: metaData:template is not updated for all Resource nodes Created: 05/Oct/12 Updated: 12/Oct/12 Due: 12/Oct/12 Resolved: 12/Oct/12 |
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | None |
| Affects Version/s: | 1.1.x |
| Fix Version/s: | 1.1.4 |
| Type: | Bug | Priority: | Major |
| Reporter: | wolf bubenik | Assignee: | Lars Fischer |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 1d | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | 1d | ||
| Environment: |
Mgnl-4.5.4-patch |
||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
Various theme resources (JavaScript, htc, CSS, images, swf) in resources-Repository. Only some of the js and css-files are migrated. For most of them the MetaData property "mgnl:template" remains unchanged (css instead of resources:css). |
| Comments |
| Comment by Lars Fischer [ 09/Oct/12 ] |
|
In my recent test the meta data content has been updated correctly (just the display in AdminCentral didn't work because of undefined resource types). Have to check again. |
| Comment by Lars Fischer [ 11/Oct/12 ] |
|
This is the approach for the non-standard resources like PNG, SWF, GIF,... In Magnolia 4.4 binary types were not supported in the resources module, but in this project it was somehow managed to load them anyway. For an automatic (and clean) conversion of these non-standard binary types we would need the original non-corrupted binary content. (At least) with the current project setup it is technically not possible to extract the original files in a non-corrupt way and put them into a newly configured node. For a conversion of such resource libraries we recommend the standard module update tasks using the InstallResourcesTask/InstallResourceTask routines. Text resources could be migrated but there should be a defined resource type for new resources before the migration (but these resources also should use the Tasks mentioned above). |
| Comment by Lars Fischer [ 12/Oct/12 ] |
|
In the M. test project the resources are freshly triggered after a server restart. In my environment, all the "known" (plain text content) resources are always successfully converted during the migration process. After restarting the server, the resources are marked as "missing" again (most likely because of the specific module behavior). For missing "text" resources, it's possible to register the corresponding resource type in the resources module configuration so that the type of the converted resource is known to Magnolia. This already works with the custom defined "HTC" resource type. |
| Comment by Lars Fischer [ 12/Oct/12 ] |
|
For the binary part:
(we would have provided a custom migration solution if this would have been technically possible) For the text part:
Recommendation:
|