[MAGNOLIA-5774] Provide a "deletable" Property for the Areas Created: 15/May/14  Updated: 19/May/22  Resolved: 19/May/22

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

Type: Improvement Priority: Neutral
Reporter: Tom Wespi Assignee: Unassigned
Resolution: Won't Do Votes: 1
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)
Date of First Response:

 Description   

Often areas are used to provide single capture content. For this areas are very useful, e.g. if the editor can edit 3 products, but no more.

So if there are some required fields in the area, once a product is captured, there is no way the delete this content.

The deletable property should create a delete button in the area bar, which deletes all content under the area node.



 Comments   
Comment by Vivian Steller [ 06/Nov/14 ]

I like the idea of deleting all contents of an area, but IMHO at least as important as deleting the area's children it's important to delete the area node itself.

Consider the following example:
We have an area "aside" which should be inherited to sub pages. Sub pages can overwrite the area (editing is not restricted to the root page). The area form contains a property marked as "required".

Now, if you overwrite the area on the sub page, you have to define a value for the required field. Fine so far. However, you can never "undo" this: without being able to delete the area node itself there's no chance to inherit the required property again. You cannot "unset" it in the dialog since it's marked "required".

+1 for deleting an area node, which would help here.

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 04:08:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.