[MGNLSTK-1487] Account for changes in resources/site modules and migrate resources in theme to be using new resource property & resource mechanism Created: 25/Jun/15  Updated: 29/Jun/15  Resolved: 25/Jun/15

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: themepop
Affects Version/s: None
Fix Version/s: 2.9

Type: Bug Priority: Neutral
Reporter: Philip Mundt Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLRES-171 Move Resource and CssFile classes to ... Closed
caused by MGNLSITE-20 Move Resource and CssFile classes fro... Closed
Template:
Acceptance criteria:
Empty

 Description   
  • Property farFutureCaching was renamed to fingerPrint
    • Property should be set to false in order to prevent log warning regarding the finger printing (not possible with old mechanism)
  • Resource links beginning with /resources should be using new ResourceServlet /.resources
    • We cannot update to the new mechanism as STK makes us of processed resources
  • Custom resources – identified by existence of class property – should not be mirgated


 Comments   
Comment by Philip Mundt [ 25/Jun/15 ]

ProcessedResources cannot be migrated to new servlet.

Comment by Philip Mundt [ 25/Jun/15 ]

Solved on branch MGNLSTK-1487-final

Generated at Mon Feb 12 07:37:02 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.