Referring to the announcement blog post
I have a question regarding the new custom field context layout: We are using vm files for rendering the content and used to have script tags inside there to execute some custom JS. With the new layout this seems to be not working anymore. As soon as there is a script tag, the code inside that tag is being executed but all code that is coming after the script block is not rendered anymore. This holds also for the case that there are several contexts set up: For the first context the content of the vm file is parsed until the end of the script block and then just stops. The content for the second (and all remaining) contexts is not rendered at all so that the table column just stays empty.
Is this on purpose? In the old UI it is working to have custom script tags so I assume that this is a bug within the new implementation?!
If this is not on purpose: What should be the workaround here and why is this not possible anymore?
An example for such a vm file would be:
<div> Something that should be displayed in the context view </div> <script> console.log('Hi there!'); </script>
In that case, the div is rendered and the statement is printed to the console. However, if there is now a second context defined, the div is not rendered there and the statement is also not printed a second time.
Is anybody experiencing the same?