Review STKTemplatingFunction exposed methods that used DamManager
(MGNLSTK-1082)
|
|
| Status: | Closed |
| Project: | Magnolia Standard Templating Kit (closed) |
| Component/s: | None |
| Affects Version/s: | 2.5 |
| Fix Version/s: | 2.5 |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Eric Hechinger | Assignee: | Eric Hechinger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | bl-145 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
website bootstrap files have to be adapted in order to add the provider id to dam references. In addition. Adapt the DemoProject version handler. It's on the resonsability to modules to perform the requested migration. So DemoProject that previously devined dms data, has to take care of the migration from dms to dam. |
| Comments |
| Comment by Christopher Zimmermann [ 18/Feb/13 ] |
|
One of the bootstraps has a lot of extra activiation information. I dont see a huge problem with that- but ideally these files should be as lean as possible. At any rate, these files need to be re-genertated to support the new 'internal' asset compositeID prefix. |