I followed the topic ClassicPress 2.1.0 Release regarding Bricks Builder problems, and i noticed that some users who received feedback and help, did actually insert the code on Bricks Builder core files
( at least from what ive read )
Code changes on plugins / themes core files will be lost upon that product next release, and if it doesnt come with the fix, it will be broken again.
In case of Bricks Builder, the advice is using the child theme from bricks, since bricks is a theme and provides a child theme.
Otherwise a plugin or a mu-plugin.
I created a simple plugin that aims to solve some dependencies problems related with Bricks Builder and ClassicPress, it is working at current versions:
I was already in touch with the Bricks team via e-mail support for some issues I discovered myself with the theme.
Thomas confirmed they’ll add extra checks and compatibility fixes in the next Bricks Builder release.
Similar actions were done with other plugins as well as I find them.
From what I can see, most of the plugins I tested so far work fine.
My personal error with Bricks was the use of “excerpt_remove_blocks” function which apparently is not defined in ClassicPress nor it’s compatibility emulation feature.
Maybe this should be added in the CP block builder compatibility fixer as well as a mocked function?