Uploaded image for project: 'Magnolia'
  1. Magnolia
  2. MAGNOLIA-4896

CLONE - Area Definitions from pages and prototype are not merged correctly

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Critical Critical
    • 4.5.9
    • None
    • templating
    • None

      In my site def template prototype, I define the inheritance of extras1 area.
      In my page def, I define the available components of extras1 area.

      It turns out that if you define the area extras1 in the page def, it is not merged with the extras1 area from the template prototype.

      To reproduce do this:

      1. Open http://demoauthor.magnolia-cms.com/demo-features/content-structure/extras-area/inherit-extras.html (Inheritance works fine)
      2. Go to the stkSection page definition and create an empty extras1 node by adding this subpath to the definition: stkSection/areas/extras/areas/extras1
      3. Reload the url above and see inheritance not working.
      4. rename new newly created node extras1 to extras1_, and all works again.

      In the code, this is the place where I found the issue happening:
      info.magnolia.templating.elements.AreaElement#isInheritanceEnabled()

      This method only gets called during the begin() method of AreaElement and it returns false if the extras1 node is redefined in the page definition.

      Thanks for quick help because this prevents our prototype/page def logic from working.

      PS: I haven't investigated if this merging problem causes other similar problems, but I imagine this could be the case.

      Stefan

        Acceptance criteria

              ochytil Ondrej Chytil
              sbaur Stefan Baur
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD