[MAGNOLIA-4162] templating: support optional areas (non-optional areas) Created: 20/Oct/11  Updated: 22/Mar/12  Resolved: 02/Nov/11

Status: Closed
Project: Magnolia
Component/s: templating
Affects Version/s: None
Fix Version/s: 4.5

Type: New Feature Priority: Critical
Reporter: Philipp Bärfuss Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

We have to support optional areas. If an area is optional it has first to be created (via a create button).

If an area is optional:

  1. if not yet created
    • the area bar has a create button
    • the script is executed
      • in the edit mode but the content object is null (otherwise we can't place the bar)
      • not executed otherwise (no place holder divs)
  2. if create
    • the bar has a remove button (other areas cannot be removed nor created)

If an area is required

  • the area node gets created (always)
  • the script is always executed
  • no remove or create button (just edit)

All kind of areas can be optional (noComponents, single, list)



 Comments   
Comment by Eric Hechinger [ 14/Mar/12 ]

Tested with 4.5.1

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