Brizy stores too much information in database's wp_postmeta table.
I have approximately 30 pages edited with brizy and it seems to be storing a lot of information in the wp_postmeta table in the database for each page. None of the tables weighs more than 10MB besides wp_postmeta, which is already at 519MB. Is this information stored in this table important? how can I avoid this extreme bulking of weight? If there is no solution i would have to redo every page with another builder since brizy doesn't seem to be viable.
-
Hello, I have the exact same problem. Is there any way we can avoid this? Thank you !
0 -
Hello, I have the exact same problem. Is there any way we can avoid this? Thank you !
0 -
We found out, there are a lot of rows of compile html. We have only few pages but metapost have over 1 Gb. Is there anythink we can do?
1 -
Unfortunately we had to give up on this builder since we got no useful information from the support team and there seems to be no solution to this issue. We are now building our page with elementor. Sorry for the late update
1 -
I seem to be encountering this very same issue. Did anyone come up with a fix?
1 -
It's not just post_meta, the database is packed with revisions as well. Sometimes the builder hangs because there are so many revisions being stored that you have to "clean" the database just to continue to use the builder. There's a ticket for this, but there hasn't been a fix. Although I like being able to go back a change or two, but at this point, I'd settle to just have the ability to disable revisions.
0 -
I had the same issue, wp_postmeta over 1 gig. WP Optimize plugin did it for me.
0
Please sign in to leave a comment.
Comments
7 comments