mhm. hopefully we really gonna see a fix and at least some info from bricks team again… its getting…
As a temporary solution, have you folks using CSS frameworks considered just adding the framework CSS into your child theme?
I don’t use ACSS or BricksProps, but I have a very small (microframework I guess), which is just a bunch of CSS variables for handling all the typography, spacing etc. And it all just lives in the child theme, then in Bricks I’m just adding in those CSS variables where i need them. There’s no lagging at all in the builder, as none of it is actually being added to Bricks, no classes added etc, it’s just a stylesheet in the child theme.
Obv not a bulletproof solution, as it appears to be that if we built pages that were sufficiently complicated, we could run into the same lagging issue eventually. But for now, it’s a pretty solid workflow for being able to use a CSS framework with no immediate lagging issues.
and its still not related to acss. 
still hoping for an answer from bricks team again.
wplit
I always use the child theme.
grafikundso
In my case it’s definitely ACSS and Frames related. I can’t tell what exactly is causing the massive lag problems. It’s not only while typing, it’s also when i try to move elements. If i don’t use ACSS and Frames and only use pure Bricks and my own classes as described above, everything is snappy and works fine.
i know. for some it’s happening with acss. but how to say, no matter what it’s related it need an asap fix and some more communication.
The problem isn’t caused by ACSS and Frames.
Frames only “fastened” the symptoms because the components are complex through their accessability.
As here already was written (and that is aready indentified by different people) the problem is caused by thr re-rendering of the objects. More complex css variables / elements are more repeatable rendering on the canvas and so a slower result. That’s why it seems that it’s caused by frames. But it’s not.
You can test this by yourself. Create a section with some cards and some css on them. Then start to duplicate them. In my case (tested by Kevin himself) with three sections with not so much complex elements you have nearly no lag) if you duplicate them to 5 and try to change inputs on the left, the lag is there and it will be become nearly unuseable.
In the other thread there are videos that document that issue and timmse and Thomas also confirmed the issue. I think it is not that easy to rework the builder logic in this case so give the guys a bit time to fix it the best way possible.
2 Likes
Frames only “fastened” the symptoms because the components are complex through their accessability.
I know, this is why I said…
it appears to be that if we built pages that were sufficiently complicated, we could run into the same lagging issue eventually
I get the core problem is Bricks related and to do with having complicated pages built. It was a suggestion for a temporary workaround for people who were wishing to use CSS frameworks, as people seem to be hitting the issue straight away before adding lots of elements. But if using a stylesheet inside of a child theme, the problem doesn’t seem to happen unless you start building out complicated pages.
I’m not suggesting the issue needs to be fixed by third-party plugins.
2 Likes
Did you try a clean WP / Bricks install without ACSS and Frames? In my case, everything works perfect, if i use pure Bricks and my own utility classes. And sure, my templates do have their own classes and i also duplicate cards etc. I didn’t run into any lag for now.
And sure, i would love to use ACSS and Frames, but at the moment the lagging makes it unusable. And i don’t want to invest in a multithreadripper super power monster pc just to do something like web development.
many of us tried blank installs and all. can you finally respect this is happening without acss? big thanks!
What do you mean with “respect”?
I can confirm that i have no problems when i use Bricks 1.6.2 with my CSS classes (around 50). I also can use Firefox to build websites with Bricks without any lags.
As soon as i install ACSS and Frames and start to use them, my browser gets so laggy that i’m not able to work with that environment. That’s really sad, because i really like ACSS and Frames.
yes respect. exactly. others facing issues without acss. and its confirmed its not related to. and you continue to tell same story. anyway, still hoping for an answer from the team.
Yes, I have run several tests with different installations/environments.
Sorry David. wasn’t targeted to you. I used the wrong answering icon. Answer was for DLR.
1 Like
Any news here?
Did a local install with BRICKS, ACSS and frames yesterday. Unfortunately still unusable, because of a very very slow interface starting to use the left panel to modify elements.
They’re on it. Just a little more patience…
OK.
But on the other side i pay for plugins that i can’t use and i can’t sell.
Hope that there is a solution soon.
bricks is still refundable. acss subscription can be pasued or canceled.
and yes all of us are waiting. patience is king. and when this is fixed a big milestone is done. so i prefer to wait for the “final” fix.
3 Likes
You bought a beta. That’s what a beta is: a fast developing tool that is able to contain more or less critical bugs.
Besides that: Of course I’m also unhappy with the situation but for smaller websites (and with a bit patience some more complex one) - you’re able to work with Bricks.
Did you check your Bricks system settings? Is everything green there?
I have no problem with Bricks. Bricks itself. Bricks works, if i use it without ACSS and frames.
Problems start if i use it with ACSS and frames together.
I don’t know what exactly causes these lagging problems, so i don’t want to blame anybody for it.
But it’s a real bummer i have to pay for software that is not usable. And i don’t see any alternatives. Oxygen is also laggy as hell and the framework behind is no longer in development. Breakdance is more for people that don’t need a pro page builder.
I hope that Bricks gets the problems solved soon, because i like the interface and i also like the idea and approach of ACSS.
2 Likes
Then write the support from ACSS. The guys are helpful. Maybe you have an additional problem.
Status quo: The lag we talk about here is not caused by acss and frames. Tested by many others including me.
2 Likes