You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have added some JavaScript functionality to the backend, and for that I used <script type="text/x-magento-init"></script>. This worked fine in 2.0.7, but in 2.1 this stopped working.
I've added it with after_element_html when creating the form:
This worked fine in 2.0.7, but in 2.1 this stopped working. When I look at the source, I simply see the raw <script>-tag there, that otherwise would have been replaced.
Now I assume my approach (misusing after_element_html to insert an entire HTML-blob) isn't the most elegant, but it worked. Until the 2.1 update.
Can anyone point me in the right direction why this stopped working or how I should implement it otherwise?
a small footnote: the html included and the JavaScript are all knockout-based. Could that have something to do with it? Since knockout is now already throwing errors on my custom html, which makes sense of course.
The text was updated successfully, but these errors were encountered:
I have added some JavaScript functionality to the backend, and for that I used
<script type="text/x-magento-init"></script>
. This worked fine in 2.0.7, but in 2.1 this stopped working.I've added it with
after_element_html
when creating the form:This worked fine in 2.0.7, but in 2.1 this stopped working. When I look at the source, I simply see the raw
<script>
-tag there, that otherwise would have been replaced.Now I assume my approach (misusing
after_element_html
to insert an entire HTML-blob) isn't the most elegant, but it worked. Until the 2.1 update.Can anyone point me in the right direction why this stopped working or how I should implement it otherwise?
a small footnote: the html included and the JavaScript are all knockout-based. Could that have something to do with it? Since knockout is now already throwing errors on my custom html, which makes sense of course.
The text was updated successfully, but these errors were encountered: