[MAGNOLIA-6341] cms and cmsfn context attributes should be bootstrapped by templating module Created: 14/Aug/15  Updated: 09/Mar/21  Resolved: 09/Mar/21

Status: Closed
Project: Magnolia
Component/s: rendering
Affects Version/s: 5.4.1
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Unassigned
Resolution: Outdated Votes: 0
Labels: bootstrap, freemaker, jsp, quickwin
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled

 Description   

magnolia-rendering bootstraps the cms and cmsfn context attributes on both the JSP and freemarker renderer configuration. The classes that they point to exist in magnolia-templating. magnolia-templating is dependent on magnolia-rendering so it should be responsible for bootstrapping those context attributes.

Please move:

  • /mgnl-bootstrap/rendering/config.modules.rendering.renderers.freemarker.contextAttributes.xml
  • /mgnl-bootstrap/rendering/config.modules.rendering.renderers.jsp.contextAttributes.xml

to the mgnl-bootstrap folder of templating to fix this issue.


Generated at Mon Feb 12 04:13:36 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.