However, the fact that the same code worked in 1.3.7 matches a similar situation that I had, where code that worked perfectly in 1.3.7 no longer worked in 1.4.0. I think that the contents of the code block gets changed somehow during the upgrade.
So this really is the exact same problem I had a couple days ago. The same code that worked fine in v.1.3.7 does not work in v.1.4.0 @timmse implied there was no problem with Bricks.
I tried my best to tell him that’s not true. Good to see further evidence that I’m not crazy.
Hi Mihail,
Thanks a lot for your report and the detailed information. We’re currently investigating what causes the changes when using the code element.
I simply said that I cannot reproduce the webfont.js error.
To be able to recognize and acknowledge an error, we must be able to reproduce it. And that was unfortunately not possible in your case until now, but Mihails Screenshot showing there’s a difference between code block and code on frontend helps a lot.
With pleasure,
but please check first whether the problem has already been reported and please create a separate thread for each problem - ideally with simple instructions on how we can reproduce it.
yep, soon I will find 5 minutes to check if anyone else has such a problem and then record each video with a demonstration of how it worked / how it works now and how I fixed the problem
We found out a possible conflict between the Dynamic Data logic and the scripts inside the Code element or inserted directly into the page content. We’ll provide a fix if not before, at least with the 1.4 stable release.
Including the code execution in Bricks Settings » Builder Access (1) + the code execution on the code element (2) itself? If so, are there any console errors?