Bricks Version: 1.3.7 Browser: Chrome latest OS: Windows 11
For some reason when upgrading from 1.3.6 to 1.3.7 there seem to be lots of duplicated CSS theme styles that have seemingly been written but overridden.
Even though they are being overridden this is still added bloat code x5. Again not sure why it happens with 1.3.7
Here’s the video of the exact same site, the exact same page showing 1.3.6 and 1.3.7:
Bro that is just crazy. I saw some strange things since upgrading a few sites to 1.3.7, and a few bits of what I assumed were extra new code. But now I want to carefully verify the code on sites before I upgrade anymore. 1.3.7 seems to be at rough release. Interested as to what you find out or what the Bricks official reply is. About to start 2 new sites today and was going to upgrade another. I will do some code comparisons and let you know if I see anything similar.
After building a new site in Bricks 1.3.7 this afternoon, I found similar code and some other unneeded code, on a basically blank page. Also found 3 more show stopper bugs in 1.3.7 today. Guess I will have to give up on Bricks for awhile, hope 2.0 doesn’t take too long hahaha. I already expressed my sentiments about 1.x code! These guys are going too fast and not testing the code very well. I would fix and thoroughly test the 400 some odd bugs first, before trying to keep adding features.
3 Current projects will have to use Oxygen or Divi for now… Hate to rebuild large complex sites down the road but I have no choice.
I’ve see this happening all the time. In the example below, I added a class to a container and set justify-content to center. 4 separate identical instances of a style rule, 3 of which are overridden.
You are of course absolutely right that such errors (among others) should definitely not happen. We have planned a lot for 1.3.7, maybe a little too much. We will definitely focus more on full testing in the future, so we can eliminate such gross blunders before the release.
Thank you for your understanding. All this will be fixed in the upcoming version, of course.
Thanks!!! And please, please slow down on all the new features and focus on code quality. A few new stable features per release or more bug fix releases would be nice.
It has been nice working with you guys for the last year since the initial release. Keep up the great work and the way you listen to the community!
We think we found the root cause for these repeated styles (and scripts). It might be related to missing SVG files in the layout. Could you check in your own servers if for the pages where you get this odd behavior you have a missing SVG file somewhere?
For me, I don’t have any missing SVGs. Here is an example of a page where it occurs (although I’ve seen it on most—and probably all pages on this site): https://pogo.infinitemonkeys.ca/pogo-case-studies/
I can provide admin access if you want to look behind the scenes.
I did notice a real nice bump up in speed which I think is due to this and the rewrite
Could I just ask with regards to the 2 sets of CSS Vars declaration? Is it standard to have all these colours even if not being used or selected in the colour palette and the same with the bg-success, danger, etc. when they have not been added?
Also is there a need to have the WP preset font size small and font size huge too?
Hey Mikel,
Thanks for the tip! Can you please provide a link so that I can take a closer look?
Where exactly did you define .heading-font? If you had created the class in Bricks, the !important would not be there and the selector would be .brxe-heading.heading-font
