WPIntell

Source evidence

Fatal Error When I Try To Activate it

Redirectioner · support · 2017-03-29T20:07:00+00:00

questionsentiment
highseverity
0.95relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

3 / 28 rows with source links

10.7% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

25 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
runningwolf resolved
Your plugin doesn’t want to re-activate on my site. I get this Fatal Error: Warning: include(): Unable to allocate memory for pool. in /var/www/html/wp-admin/includes/plugin.php on line 1882 Warning: require(): Unable to allocate memory for pool. in /var/www/html/wp-content/plugins/404-redirected/404-redirected.php on line 56 Warning: require(): Unable to allocate memory for pool. in /var/www/html/wp-content/plugins/404-redirected/404-redirected.php on line 57 Parse error: syntax error, unexpected ‘[‘ in /var/www/html/wp-content/plugins/404-redirected/includes/admin.php on line 793 How can I fix this? I updated the plugin and it caused an error, so I wiped it off my installation (via FTP) and reinstalled the newest version and now it refuses to activate again. It’s possible your seeing this because of cache, so if you can empty all your servers’ caches (static & memcached being the most important ones) that would be the first thing to try. If the issue persists, please report back here. It turns out your WordPress site is using an old PHP version which was causing the issue. We’ve released version 1.4.9 just now that mitigates the issue you were experiencing. Update to it and you should be fine again. You should, by the way, really start moving your site to a newer version of PHP. You can read here about why it’s smart on many levels to move to a newer version of PHP. Thanks, everything is sorted now 🙂 You rock! Cheers!

Comments

4 shown
Remkus de Vries 2017-03-29T20:40:00+00:00

It’s possible your seeing this because of cache, so if you can empty all your servers’ caches (static & memcached being the most important ones) that would be the first thing to try. If the issue persists, please report back here.

Remkus de Vries 2017-03-30T15:10:00+00:00

It turns out your WordPress site is using an old PHP version which was causing the issue. We’ve released version 1.4.9 just now that mitigates the issue you were experiencing. Update to it and you should be fine again. You should, by the way, really start moving your site to a newer version of PHP. You can read here about why it’s smart on many levels to move to a newer version of PHP.

runningwolf 2017-03-30T17:20:00+00:00

Thanks, everything is sorted now 🙂 You rock!

Remkus de Vries 2017-03-30T18:10:00+00:00

Cheers!