Long hesitated to upgraded from Bricks 1.11 to v2 and here and there I know why…
For instance all code elements that are signed will show: [object Object] when the template is opened up again. There is no issue with the code itself and it is correctly displayed on the fron end. It seems to me that Bricks is forgetting that the code was already signed.
What is up with the Bricks code element with v2?
Hi @Mike8040,
Can you record a short video of the issue and how to replicate it? I’ve checked a few of my code element instances that I use, but could not replicate the issue.
Best regards,
Matej
Hello,
it is just opening a template and looking at the wording [object Object] where the content of the code element should appear instead. I don’t see what the hassle of video screen grab can give more information. Both code elements have a completly different purpose and are not related. One of it is a simple CSS marquee.
The [object Object] disappears when I resign the code again. But right now I’m allowed to do it on every opening of the template or ignore the [object Object]
When you say:
[…] all code elements that are signed […]
Does that mean they were signed before the upgrade from v1 to v2? Or did you resign them after the upgrade?
Hi @Mike8040,
the point of video is that maybe we will see more informations - I usually ask for it if I can’t replicate the issue, and I can’t replicate it here. If it’s only happening with “old” code elements and not with new ones, then I agree, there is no point in video, as you don’t have steps for us to replicate it.
You could try to regenerate the signatures with the button that you see in the screenshot that was posted above.
Matej
