[MGNLSITE-84] ReferencingPrototypeTemplateSettings doesn't cope with site variations Created: 30/Aug/17  Updated: 04/Sep/23  Resolved: 04/Sep/23

Status: Closed
Project: Magnolia Site Module
Component/s: None
Affects Version/s: 1.0.8
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Zdenek Skodik Assignee: Rishab Dhar
Resolution: Inactive Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLSITE-54 Site Prototype in YAML Closed
relation
is related to DOCU-2457 Explain what the 'variations' propert... Closed
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
Date of First Response:
Epic Link: Support
Team: DeveloperX

 Description   

This is an old ticket

Having default prototype as YAML and site variations stored at JCR ends up in troubles with instantiating the ReferencingPrototypeTemplateSettings upon site merge for the variation to be rendered:

org.apache.commons.proxy.exception.ProxyFactoryException: Proxy class cannot extend info.magnolia.module.site.templates.ReferencingPrototypeTemplateSettings, because it has no visible "default" constructor.

One can either move the default prototype back to JCR or introduce the default constructor on her own to workaround it.



 Comments   
Comment by Christopher Zimmermann [ 04/Sep/23 ]

Closing as inactive. See support ticket.

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