At the moment, when a pattern fails to render, the failure is typically handled gracefully in the {{pattern}} render element by swapping in a {{pattern_error}} render element to prevent failure of the full request and conditionally show additional failure debugging information if appropriate. While this is an improvement over the previous situation where the full request would fail, it can result in render failures being masked and remaining undiscovered since the top-level request finishes successfully and no errors are logged.
To address this, a new feature to dispatch an event when a render failure occurs would allow for sites to react to these failures in various ways appropriate to their use cases. Within the module itself, the current solution replacing in the {{pattern_error}} element could be moved into a low priority subscriber. Specific site implementations could then implement their own event subscribers to either handle the failure differently or log the failure appropriately for detection and later resolution.
Implement a new render failure event for dispatching when patterns encounter exceptions during rendering
Move existing logic to replace failed pattern renders with a {{pattern_error}} element into an event subscriber
Maintain existing behavior where a failed render in the {{pattern}} element is ultimately replaced with a prepared {{pattern_error}} element
Ensure existing compatibility with {{patternkit_devel}} is maintained
Add support for subscribers to react to render failures and potentially replace in alternative content to be displayed
None
Active
9.1
Module Core