burningthumb

@patsky There is a plugin called Display PHP Version (https://www.ads-software.com/plugins/display-php-version/) which will show you on your WordPress > Dashboard > Home > At a glance, the PHP version like 7.4.x.

For me, if x=16 it works (I believe I saw a post where x=15 also works), for me if x=10 as in 7.4.10 I get the error. I don’t know if you are using a different version of 7.4.x than me but if so that may help narrow the issue down. It looks to me like a PHP problem that the plugin developer should be able to work around since every other plugin does not have the problem.

Glad its working and as @zymeth25 says if you are not using the widget it should be fine.

I disabled all plugins and started activating them one at a time until I hit this one. I did not go back and do it again with just this one active. I talked to the site owner and she told me they are not using this plugin any more anyway so for me, its a wrap, hopefully someone else that needs it can take it from here.

• This reply was modified 3 years, 5 months ago by burningthumb.

That did not work.

However I noticed that list-category-posts.php includes the file on line 33:
require_once 'include/lcp-catlistdisplayer.php';

So if I comment out line 6 in include/lcp-widget.php:
//require_once 'lcp-catlistdisplayer.php';

Then the plugin activates, not sure if it works, but it activate ??

Maybe that’s a clue.

• This reply was modified 3 years, 5 months ago by burningthumb.

Every other plugin, I use quite a few, worked. So I’m not sure what is going on with this one and that version of PHP. I did try with PHP 7.2, 7.3, and it was only when I went to 7.4 (specifically 7.4.10) that the problem happens. So its really strange. I had to solve it before June 29 and for now the only solution is to disable this plugin.

I did that. All the files are there.

I looked at it in much more detail.

I manage two sites.

One is on PHP 7.4.10 and the other is on PHP 7.4.16. Its working fine on PHP 7.4.16 but on PHP 7.4.10 the above error is reported and WordPress refuses to activate the plugin.

In my case the entire site went down and it took me several hours to narrow it down to this plugin.

So it may well be a bug in PHP but maybe you can work around it. I also raised the issue with the hosting company (telus.com) because they plan to force this version of PHP on all of their customers on June 29.

This plugin totally F-ed up our site. I finally had to disable all plugins and try to re-activate them one at a time. This one fails to active, with the above mentioned error when using PHP 7.4. Our hosting provider is forcing us onto PHP 7.4 so we have no choice but to stop using this plugin.

In the end I installed the Wordfence Assistant and used it to clear the WP Database, then I was able to activate the plugin and re-configure it from scratch.

• This reply was modified 4 years, 5 months ago by burningthumb.

I enabled debugging and re-installed the plugin now that is not active and I just get this error when I try to activate it:
Plugin could not be activated because it triggered a fatal error.

Noting in the logs… at least nothing in the debug log… if you want me to look elsewhere just let me know as I can re-create this problem all the time.

If it helps, I manage 2 sites, one hosted on godaddy and one hosted on telus. Only the one on godaddy is having the problem. As I said in my previous post, WP Security works fine but wordfence does not.

I just updated my site plugins and started getting this same error. I could not access the admin panel. I had to shell in and manually disable wordfence. I re-installed it from the admin panel and immediately got the problem again. So I again had to manually disable it.

So I have installed WP Security.

Turns out unzipping the files works so I looked at godaddy cpanel settings for PHP and zip is not included by default. I’ve turned zip on and hopefully that will fix it.

I had this same problem. About a week ago Contact Form 7 just stopped working. So I installed a different contact form plugin and it too did not work. So I installed the Postman plugin, leaving it with its default settings (except I turned logging off) and now it works again. Go figure.

I have this same issue. Is there any solution?

Hey Aaron,

Thanks! This is, of course, a much better solution and will help me migrate all of my old pages seamlessly.