If a user tries to edit or view a page that contains a macro which has thrown an exception (a common occurrence after some upgrades or among less stable macros), they receive a unhandled exception error and have no method to go back and edit the page to remove the macro, or even to delete the page. Otherwise, it appears to me an administrator has to go in and disable the macros used (which is not always easy to tell which ones were without being able to edit the source). Some functionality to address this is would be extremely valuable. For instance, an option on the page where the exception occurs to turn off macros for that page, which could be re-enabled later.