[MGNLSTK-308] Freemarker errors in paragraph templates should behave - such that it is still possible to delete the erroneous paragraph. Created: 02/Mar/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Boris Kraft Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File freemarker paragraph error.png    
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

If for whatever reason a paragraph has a Freemarker error, it would be nice if the paragraph can still be deleted (without going through the JCR Browser). Right now, if I create a document teaser inside a teaser group, it will through an error. Unfortunately, the error results in the fact that the edit bar is not or only partially rendered, so that I cannot delete said paragraph. It would be good if that can be handled in such a way that whatever happens doesn't affect the ability to delete a paragraph.



 Comments   
Comment by Philipp Bracher [ 03/Mar/09 ]

This is not easy to achieve as the edit bars are rendered inside the paragraph. This is a rather new approach and has several advantages. Still it is a valid point. Either we have to make the paragraphs more error prone, or we have to find a solution (render edit bar on error). The latter solution could lead to some wired behaviors too (in case it is not foreseen to render an edit bar).

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 07:25:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.