[MULTISITE-62] Fallback site definition should not extend the travel Created: 25/May/16  Updated: 19/May/22  Resolved: 19/May/22

Status: Closed
Project: Magnolia Multisite Module
Component/s: None
Affects Version/s: 1.2.3
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Ondrej Chytil Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: 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
Date of First Response:

 Description   

If both Multisite and Travel demo modules are installed the fallback site definition is extending the travel site definition. So any "siteless" request is then using travel site in the end. That causes at least one nasty issue, any site-independent page template is unusable by default.
There are of course some workarounds:

  • make the template available under fallback directly
  • extends override templates under fallback

But we still support the concept of freemarker and jsp page render types so this should not be necessary and in the end fallback site definition should not rely on any other site definition.



 Comments   
Comment by Roman Kovařík [ 19/May/22 ]

Hello,

This ticket is now marked as closed due to one of the following reasons:

  • A long period of inactivity
  • Uses an old or Beta version of an application, module, or framework that we no longer support
  • The issue is no longer reproducible or has been fixed in later versions

If you are still facing a problem or consider this issue still relevant, please feel free to re-open the ticket and we will reach out to you.

Thank you,
The Magnolia Team

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