Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Velocity errors in the container should not break the render of the page #15640
We need to make sure that when we have velocity parsing issues in our container code the page is able to render and when a parsing velocity error occurs and we are in edit mode an error event should be fired in order to be capture by a component error on the client in order to allow the user to know that the problem is.
changed the title
Velocity errors in the container should not break render of the page
Dec 3, 2018
When you are in edit page and cause an error in a simple widget, and close the edit content modal, we are refreshing the content, but not receiving a WS event in order to show the toast notification until you refresh the page, we need add this notification on this resource
This might seem like a nitpick but I noticed that the exact same error message appears twice for the same content instance.
Then I Create a template using the template designer. Include the container with the broken code.
In this scenario, I get the error message multiple time when I visualize the page on Edit-Mode