the site gets rendered only half-way through (up to the widget that caused the exception). This prevents us from actually fixing the broken widget, so once broken it stays forever broken. What we must do instead is - if a widget rendering throws exception we must simply catch it, and not display the widget, but continue rendering the rest of the page. Also if you are in live edit we can rendere big red sign "ERROR: exception msg" so that the user can see something is wrong and fix it in the console
At the moment if an exception like this happens:
https://gist.github.com/gochev/4354b79fea0991024608
the site gets rendered only half-way through (up to the widget that caused the exception). This prevents us from actually fixing the broken widget, so once broken it stays forever broken. What we must do instead is - if a widget rendering throws exception we must simply catch it, and not display the widget, but continue rendering the rest of the page. Also if you are in live edit we can rendere big red sign "ERROR: exception msg" so that the user can see something is wrong and fix it in the console