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].
We are receiving the allowed memory exhausted error, but our settings have already been maxed to 512GB. Further, If we disable all plugins and re-enable one by one, Page Builder is the only one which initiates this error even when it is the only plugin active.
We have not yet upgraded to WordPress 5. Since Page Builder is essential to our current design/functionality, is it time to just move on to WP 5 and get with Guttenberg or is there still support and an answer for our issue when it isn’t as simple as just increase the memory allocation in wp-config and with our wen host?
Many thanks.
Hi KFilm,
It sounds like you’re experiencing a memory leak. To confirm, does this issue occur for all pages or just a specific page? Does this issue occur when you temporarily change theme? Does this issue occur when all non-SiteOrigin plugins are deactivated?
Please note that our plugins are compatible with WordPress 5.0 and Block Editor (ie. Gutenberg) so I would try updating to see if that helps.
Hello Alex,
After carefully stepping through restores and trying different plugin combos, settings, etc. I am now thinking this was due to a corrupt database. Our site has now been running for several hours without issue (cross fingers). I will keep an eye on it and mark this thread as resolved if it continues to be in the clear. I had one instance of the issue reoccurring but after another restore I haven’t seen it again yet.
To be clearer (I couldn’t edit my initial post while it was awaiting approval) the error happened when I was trying to log into the WordPress admin panel. This particular error would only show when trying to go to the admin panel. The site itself gave an error something like “”the max byte array has been exceeded””…or something to that effect…followed by what appeared to be lines of debugging/errors. This was still memory related though and every page on the site showed this error instead.
I ran through a lot of combos of restores, plugins, theme, etc. late last night after my post. I *think* changing the theme at one point stopped the error, though I think it was in part because there was a footer on our page which used Site Builder in our main theme, but the theme I switched to had no equivalent and so it wasn’t run/displayed. Thus the issue wasn’t triggered under the alternate theme.
The issue did not occur at all with the Site Origin plugin disabled. More specifically, the Page Builder plugin was the hinging point of whether or not the issue would arise. The Site Origin Widgets plugin could be active and not raise the issue.
Good to hear on the WP 5 compatibility. We are initiating a test database to try 5 and see how it goes.
Many thanks!
Hi KFilm,
It’s great to hear that you may have found the cause of this issue. Let me know if you run into any issues and we’ll pick this back up.
Hello Alex,
Our site has been up for more than 24 hours now without issue, so I will chalk it up to a database issue.
Many thanks!
Hi KFilm,
Great to hear! :)
Please be sure to post another thread if you have any other questions.