Uploaded image for project: 'Magnolia Standard Templating Kit (closed)'
  1. Magnolia Standard Templating Kit (closed)
  2. MGNLSTK-951

Disabling ExtrasArea without need to define class property: BodyClassResolver should first check if enabled, then cast.

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Major
    • 2.0.3
    • 2.0, 2.0.1, 2.0.2
    • base system, themepop
    • None
    • Yes

    Description

      Disabling the extras area is the most common use case on templates, besides reconfigure it.
      When disabling the extras area by adding the property enabled=false, a class cast exception happens in the BodyClassResolver.
      Without the definition of the specific bean by the class property, the code does not work.
      But it is really really hard for people to find out why they get the freemarker error without the class property, and then to find out what class to use.

      The new code uses first a default AreaDefintion for checking the .isEnabled() value, and then casts within the if.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                ochytil Ondrej Chytil
                cringele Christian Ringele
                Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved: