Notice: This thread is over two years old; the information may be outdated. Please consider creating a new thread if you require free support. If you have an active SiteOrigin Premium license, you can email our premium support desk at [email protected].
Is there a way (perhaps by looking for something distinctive in the database) to determine whether a site currently has any pages using PageBuilder, and if so, which pages?
I have discovered that the current versions of PageBuilder and WPML have some sort of compatibility problem, which is affecting one page on one site I manage, even though that page doesn’t even use PageBuilder (weird!). I looked at a few pages that I thought might be using PageBuilder, but they aren’t. But before I disable it permanently on that site, I want to make sure it is not being used somewhere. If there is a way to determine that without looking at every page in the editor, let me know.
Hi OsakaWebbie,
Preface: We’re not aware of any compatibility issues with WPML – could you elaborate on the issues you’re experiencing?
Any page that has Page Builder enabled will have a postmeta with a meta_key of panels_data. This means that to check if a post has page builder enabled, simply check for that post meta. A quick SQL query would be something like this:
(be sure to change the prefix if required)
Thanks, Alex, for the clue about what to look for in the data, and that might come in handy someday. But meanwhile I found the problem – it was a memory shortage. The default setting in WordPress is lower than the WPML recommendation – the site ran at that lower setting for a couple years but then something tipped it over the edge on one particularly complex page, only in the second language (which, I have now learned, uses more memory to build in WPML than the default language). The error indeed said it had run out of memory, but I thought it was an infinite loop, not a true shortage. The page would run if both Page Builder and Yoast SEO were disabled (and no other combination was observed to make a difference), and I suspected the newest version of WPML was messing something up. But with the help of a WPML support person (who did say that Page Builder and Yoast were compatible as far as they knew), we got to the bottom of the issue, and after increasing the memory setting in wp-config, the site is running fine now.
Hi OsakaWebbie,
Glad you to hear you managed to figure out the issue with the help of WPML. I’m, sorry I wasn’t able to be of assistance this time but hopefully the SQL will help in the future somehow. Please be sure to post another thread if you have any other questions.