SOLVED: States (pseudo-classes) strange bug after import a template

I didnt use any pseudo in this website.
My friend sent me a template section where he added plus pseudo classes states. (:before, :after, :hover:before)

After I improrted hes json template section all of the states are gone from drop-down options and only showed the :before state.

If, I deleted the :before state, saved the template and refresh the editor, gone back the default states again.
After I added manually again the states (:before, :after, :hover:before) and working everything again.

I tried it from zero step 3 times and I can reproduce this bug 3 times.

image

Hi,
Thanks so much for your report!

Would you be so kind as to provide us with a screencast using https://jam.dev showing and explaining what’s happening so that we can ensure that we use the exact same steps? Also, having the mentioned template at hand would be helpful, too.

Best regards,
timmse

Hi Timmse!
Please ignore the end of the video, where I entered the pseudo classes again, because I made a mistake. However, the rest of the video is relevant! You can see that if I import a template that has several “unique” (ie not default) pseudo classes, the system gets confused.

https://jam.dev/c/c58e25ef-0e69-4495-8a83-b68c755753d8

Hi,
Thanks for the video!

The problem is not that the pseudo classes/elements are “unique” but concatenated. This is currently not supported (or did it work in a previous version?). I have created an improvement task for this.

1 Like

Please excuse me, but I’m not sure I understand what you’re writing.
By concatenated, do you mean that e.g. :before:hover doesn’t work?

But it works. That’s not my problem. My problem is with the import part. If the template to be imported contains extra pseudo classes, the original classes are also deleted, as you can see in the video, and it does not import all individual classes.

BUT! IF I manually delete the individual classes after import, I see the default ones again. Then I manually upload the individual classes again and they work flawlessly!

As soon as such a concatenated selector is included, there is a problem. Not with “simple” selectors - at least, I cannot reproduce it. But…

You don’t have to :slight_smile: The problem has been confirmed, and we are trying to fix it as usual.

1 Like

Hi @simplecreative ,

We’ve fixed this in Bricks 1.12 BETA, now available as a manual download (Bricks – Account)

Please let us know if you are still experiencing issues.

You can see the full changelog here: Bricks 1.12 Changelog – Bricks

As with any beta release, please do not use it on a production/live website. It is only meant for testing in a local or staging environment.

Best regards,
Matej

1 Like