Problem with WP Plugin. (Shared Hosting)

Status
Not open for further replies.

xdude

New member
Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 12288 bytes) in /home/xdude/public_html/wp-content/plugins/wordpress-seo/inc/sitemaps/class-taxonomy-sitemap-provider.php on line 76
Fatal error: Allowed memory size of 41943040 bytes exhausted (tried to allocate 3200 bytes) in /home/xdude/public_html/website.com/wp-admin/includes/template.php on line 441

Different error locations but the same error on both sites. Looks like the same old memory exhausted problem.
 

Genesis

Administrator
Staff member
Which version of Jetpack did you use @xdude? I checked WordPress and someone with the same problem got it solved by using a more recent version of the plugin. This one seems to be the most up to date one - is this the one you're using?
https://jetpack.com/2018/08/07/jetpack-6-4-release/
Source of discussion: https://wordpress.org/support/topic/jetpack-produces-white-screen/

With Yoast - maybe @un4saken could help:
Problem Resolution
This issue is caused by a missing dependency. Yoast SEO now requires the php-bcmath library.

If you're on a shared server, you'll probably need to ask your hosting provider to install the missing library. If you're on your own virtual server or a dedicated machine you can fix the issue by installing the php-bcmath library. For example on CentOS servers you would run:
PHP:
yum install php-bcmath
Source: https://clients.websavers.ca/whmcs/knowledgebase/211/WordPress-Yoast-SEO-plugin-blank-screen.html

Another person solved the problem with removing a javascript optimizer plugin:
So people then started to think it may have to do with javascript conflicts.
Source: https://wordpress.org/support/topic/blank-edit-window-after-update/
 

xdude

New member
Thanks @un4saken

From there I did upgrade the PHP version to 7 and it seems worked too. Now all problems are gone and all 3 sites work perfectly. Maybe when PHP version upgrades memory limit also increases ? or it might be something else which got sorted in newer version of PHP. Anyway I'm glad it's all sorted out and sites working like those should be.
 
Status
Not open for further replies.