[MULTISITE-15] Multisite module does not rewrite "extends" path Created: 20/Jan/14  Updated: 30/Jan/14  Resolved: 21/Jan/14

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

Type: Bug Priority: Neutral
Reporter: Magnolia International Assignee: Philip Mundt
Resolution: Fixed Votes: 0
Labels: None
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:
Epic Link: migration_to_5.2.2

 Description   

Multisite module has been moved from extended-templating-kit to multisite.

When upgrading an Magnolia instance to 5.2.1 with a site which extends another site using an absolute path, the site will not work since the path is not updated.

For instance:

Before upgrade

  • modules
    • extended-templating-kit
      • config
        • sites
          • site1
          • site2
            • extends /modules/extended-templating-kit/config/sites/site1

After upgrade

  • modules
    • multisite
      • config
        • sites
          • site1
          • site2
            • extends /modules/extended-templating-kit/config/sites/site1


 Comments   
Comment by Roman Kovařík [ 29/Jan/14 ]

commit:
https://git.magnolia-cms.com/gitweb/?p=enterprise/multisite.git;a=commitdiff;h=1228aa981fd215a306d5498fa7109ed203b1fe23

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