Unable to save in Bricks Builder after updating to 1.24.1

I encountered a similar situation. After the MetaBox-AIO plug-in was installed and worked for a period of time, all the saving functions of the entire WP system would be stuck. Finally, I closed the plug-ins in the AIO one by one. After stopping the Revision plug-in, everything was normal. I'm not sure if there's something wrong with the plug-in or the database, but I've tried reinstalling the entire WP and the same thing happens. Usually the save exception occurs after a short period of time. In short, this is the only thing I can try now, which is to turn off the Revision function.

You're welcome~

I stupidly just deactivated my usual plugins and template editor to find out the reason. . . Except metabox-AIO......, then I reinstalled wordpress countless times, until I was almost exhausted that I realized there was some plugin in metabox and discovered the problem.

Anyway, glad our problem is solved, cheers~

Hi Peter,

I have followed your link and sent a report to bricks. I did not realize the possibility of a bug in Bricks Builder until your reply, because the save failure is not limited to the builder.
Anyway, I've gone into the details as far as I know.

https://forum.bricksbuilder.io/t/wait-bricks-not-saving-when-metabox-aio-plugin-is-activated/19180

Here I repeat my report to Bricks:

------------------------------------------------------------------------------------------------------------------------------
(My report details) The method to reproduce is simple:

No matter what the situation, just turn on the Revision plug-in
The save function will not be disabled after Revision plug enabled
It has nothing to do with other third-party plug-ins. My WP test environment only has two plug-ins, Metabox and AIO. (I have Bricks builder theme and child theme)
Not sure if it is related to the theme, but I am using BricksBuilder, and I also tried to uninstall Bricks after the save function failed.
All WP system-wide saving functions will be disabled, except for the saving function within the metabox plug-in.
Depending on the number of actual work modifications and saves, WP or editor Save will generally fail after one to a few hours.
Saving is sometimes effective, but the save button will always display the status of waiting to save (for example, the button keeps rotating). Sometimes the save can be successful if you manually exit the page, but this is not guaranteed, and there are exceptions. For example, if you modify the tag or taxonomy in CustomPostType, you will definitely not be able to save it.
I have tried reinstalling a clean WP, and also tried exporting the database and reimporting it, but none of them solved the problem.
My test environment is Local by FlyWheel (Linux)
The browser is Google Chrome lastest (Linux)

Peter,

After two attempts, I cannot reproduce the installation error message.
I cannot recall the conditions. I only recorded the error message at that time. I am not a technical person. I will not tell whether this information will lead to the wrong debugging direction of Metabox and Bricks. Please make your own judgment.

Warning: An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums. (WordPress could not establish a secure connection to WordPress.org. Please contact your server administrator.) in /home/admin/Local Sites/mk1/app/public/wp-includes/update.php on line 211

Same, Bricks support just said I should roll back AIO.

I also have the same problem with Metabox AIO 1.24.1 in Bricks. Disabling the MB Revision extension solves it for now.

Bricks reported NO BUG

em…

We can only do one thing, which is to wait for mb or bricks to proactively discover the problem.

Attention, I found that if the revision extension has caused problems before, don’t be like me and think that turning off the extension can solve the problem, because some data writing errors have occurred, which I discovered later, so everyone should check carefully