[MGNLRES-179] Migrate all resources from templates to resources Created: 14/Jul/15 Updated: 29/Mar/22 Resolved: 26/Oct/15 |
|
| Status: | Closed |
| Project: | Magnolia Resources Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 2.4.2 |
| Type: | Story | Priority: | Critical |
| Reporter: | Magnolia International | Assignee: | Philip Mundt |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | requires_documentation | ||
| Σ Remaining Estimate: | 0d | Remaining Estimate: | 0d |
| Σ Time Spent: | 3d 3.25h | Time Spent: | 3d 3.25h |
| Σ Original Estimate: | Not Specified | Original Estimate: | Not Specified |
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||||||||||||||||||||||
| 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)
|
||||||||||||||||||||||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||||||||||||||
| Epic Link: | Phase out in-place templating app | ||||||||||||||||||||||||||||||||||||||||
| Sprint: | Basel 17 | ||||||||||||||||||||||||||||||||||||||||
| Story Points: | 13 | ||||||||||||||||||||||||||||||||||||||||
| Team: | |||||||||||||||||||||||||||||||||||||||||
| Description |
|
Timebox: 2 days With If one upgrades to 5.4, and freemarker config wasn't customized, templates will be loaded solely via resources API - so it's pretty confusing to have an app that lets one edit the"templates" workspace, but never gets used. I'd suggest the inplace-templating module is now unnecessary:
This issue obviously needs to be replicated in MGNLINTEMPL; issues from MGNLINTEMPL might need to be moved to MGNLRES (some are probably redundant) |
| Comments |
| Comment by Philip Mundt [ 17/Sep/15 ] |
|
Templates from templates workspace have the following properties:
|
| Comment by Mikaël Geljić [ 18/Sep/15 ] |
|
All fine to remove install tasks on 5.4, but careful about 5.3: |
| Comment by Mikaël Geljić [ 18/Sep/15 ] |
|
We need a proper flow diagram on how to react to various cases:
Side note:
Besides, if we actually do cleanup w/ templates that do not need to be installed anymore, how about doing that for installed resources too? (out of consistency) More questions:
|
| Comment by Philip Mundt [ 05/Oct/15 ] |
†emplates workspace:Does not contain any information about the extension. Shall we always consider ftl? /mte/templates/pages/main /mte/templates/pages/main/autoImport=true /mte/templates/pages/main/text=CONTENT /mte/templates/pages/main/enabled=false resources workspace:Contains information about the extension depending on the type. mgnl:template available by default (using any *ResourceTask: /sample-css /sample-css/text=CONTENT /sample-css/mgnl:template=resources:processedCss extension property for binary resources (installed using info.magnolia.module.resources.setup.InstallBinaryResourceTask) Examples via resources-app upload:
|
| Comment by Philip Mundt [ 06/Oct/15 ] |
Template migration procedure
Function "Migrate to resources":
|
| Comment by Philip Mundt [ 22/Oct/15 ] |
|
Re-opening due to changes in actual migration-process |