Soon, we are currently preparing a hotfix 
Matej
3 Likes
This is great to hear that it’s coming soon.
I know I’m probably just stating the obvious here so please forgive me… I’m incredibly shocked something such as this - affecting styles as fundamental and popular as gradient overlays - got past the QA tests. I really hope this type of check is added to the suite of automated tests that I’m (hoping) run when making new code commits so that this type of upgrade issue is avoided in the future. I’m positive your team already knows this so I apologize, it just seems like an issue that should have easily been caught, so I wanted to just make a friendly reminder. 
Us users just really want to avoid Elementor-style upgrade trauma after all, lol. 
Hi guys,
We fixed this issue in Bricks 1.12.3 by reverting to the previous behavior because the (well-intended) changes have caused unforeseen problems in too many places. We apologize.
If you have already added temporary fixes (see Matej’s answers), please remove them.
The update is now available as a one-click update in your WordPress Dashboard.
Changelog: Bricks 1.12.3 Changelog – Bricks
Please let us know if you are still experiencing issues.
Best regards,
timmse
3 Likes