SOLVED: Pseudo-classes are empty when importing a template from remote website

Bricks Version: 1.5

Hello Bricks Team,

When I import a template from website(B) with pseudo classes then the pseudo classes do not import with it. Like ::before, :hover, :hover .className ect

On website(A). I see the template I imported but not the pseudo-classes.

3 Likes

Thats a pretty big bug - great discovery Daney if it is indeed validated/ reproduced.

2 Likes

Hi Daney,
Thanks so much for your report!

Weā€™re already aware of the issue. Pseudo-classes are not exported/part of the template, as they are global data. Right now, you need to create the pseudo-classes if they are missing manually.

So, for example, if you have a button that should have a hover state, select the button and assign :hover to it. The hover-styles should still be present.

Weā€™ll tackle this in a future release to automatically create non-existing pseudo classes when inserting a template.

Best regards,
timmse

3 Likes

Is this coming in the next update 1.5.1 by chance?

Thanks! :raised_hands:

No, unfortunately not in 1.5.1.

Well, as long as itā€™s fixed in a future update. All good. :slight_smile:

This is supposedly fixed as of 1.7.1. :slight_smile:

Hi guys,
With Bricks 1.7.1, now available as a one-click update in your WordPress Dashboard, pseudo Elements like ::before or ::after and pseudo Classes like :hover or :first-child will be imported/created when importing a template.

Please let us know if you are still experiencing issues.

Best regards,
timmse

3 Likes

I am having this same issue in version 1.9.6.

Hi Luke, welcome to the forum!

Unfortunately, I cannot reproduce the issue. Would you be so kind as to provide a screencast using https://jam.dev showing and explaining whatā€™s happening?

same here with Bricks v1.11

the style data was imported and I could ā€˜activateā€™ it by manually inserting the ā€œ:beforeā€ pseudo class on the container. guess in the dark: maybe itā€™s because we use ā€œ:beforeā€ instead of ā€œ::beforeā€? :wink:
dontā€™ have time to reprocude the issue right now, maybe next week.