Allow fragment developers to configure error handling template

• Type: Feature Request
• Status: Under Review
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: None
• Fix Version/s: None
• Component/s: Portal Services > Templates Engine
• Labels:
  • Fragments_development
  • Liferay_Online
  • Security
  • evaluateTechnicalEffort

Currently if the fragment processing encounters a freemarker error, the freemarker exception cause is printed to the DOM which could reveal information that should be hidden

As a fragment developer I would like to be able to configure how errors are processed in fragments as I can currently for web content and ADTs