WAIT: Custom CSS Stops Working and Auto-Save Fails

Bugs
1

Browser: Chrome Latest Version
OS: macOS - Sequoia 15.2

Hey, I’m running into a couple of issues with Bricks Builder:

  1. I applied custom CSS to a parent container, saved it, and when I came back the next day, the styles stopped working even though the CSS is still in the custom CSS folder. The only way I’ve been able to get it to work again is by applying the same CSS to individual child elements instead, which is frustrating and inefficient—especially with shared media queries.

  2. Revisions aren’t saving consistently. I’ll click “Save,” but when I check Revisions later, it doesn’t always detect my changes.

Would appreciate help figuring this out because it’s slowing down my workflow. Thanks!

2

Hello,

Can you make a screenshot to which element you applied the custom CSS (and what is the ID or class, that you applied it to), and a link of the website, so I can check it?

By “doesn’t detect changes”, do you mean that there is no revision created, or something else?

Thanks,
Matej

3

Hi,

Is it ok if I give you a link to a site that’s in development and not yet live?

What I mean is that after having manually saved, the system will not register my most recent save attempt when I go into the revisions menu and I’ll find that there is a significant time jump between my most recent save and the last revision that is listed on in the revision queue.

4

Yes, please. I just need to see the custom CSS, and why it’s not applied.

So, if you add a new element, let’s say basic text, and then you maybe change the text, and save. IF you open revisions, you don’t see it?

5

Certain plugins or themes might interfere with the normal operation of WordPress revisions, especially if they’re performing automatic saves or custom caching of revisions.