Setting an XSLT transformation after an invalid XSLT has been set is not possible.

[MatthijsSmets]

Issue

Setting an XSLT transformation after an invalid XSLT has been set is not possible.

Steps to reproduce

Using the new ladybug frontend:

• Open the settings modal by clicking the gear icon
• Add something to the transformation to make it invalid like:

    <xxx/>

• Save it.

• Open a report

• See that an exception is visible in the editor:

• Close the report
• Click the reset to factory settings to reset the transformation to a valid XSLT or set it manually
• Make sure the Use transformation for report.xml option is checked
• Reopen the report
• See that the exception is still visible

Only unchecking the Use transformation for report.xml option fixes this problem, but it means a custom transformation can not be used.

Notes

• This only happens with the new ladybug frontend, so there's probably something wrong in the API.
• Restarting the backend fixes the problem