Premium version causes critical error

Same here. I renamed the folder via FTP, and the site came back up.

Same issue here with MC4WP: Mailchimp for WordPress Premium (version 4.8.11) Forced my sites into recovery mode. For the time being, I disabled the plugin till the issue is resolved and exited recovery mode. I’ve contacted the developer at https://www.mc4wp.com/contact/ where we should go for premium support. I haven’t yet heard back.

• This reply was modified 4 years ago by evit.

We also had this happen upon update from 4.8.10 > 4.8.11. I hope we don’t have to wait for a fix until after Thanksgiving. The free version of the plugin, which we also have installed, appears to be functioning normally.

Hello everyone,

I am sorry for the error. It was there for only a few minutes due to an issue in our automated release script and it seems you were unlucky enough to update in that short window of time. If you re-download version 4.8.12 from our website now then the issue should be gone.

If your website is currently still experiencing issue, please manually deactivate the plugin by renaming the /wp-content/plugins/mc4wp-premium/ directory.

After doing that you should be able to safely upload the latest version again by either following the original installation instructions or by manually updating to the latest version.

We’re sorry for the hiccup and trouble this caused. Let me know if there’s anything we can do to help get things running smoothly again.

Danny

• This reply was modified 4 years ago by Danny van Kooten.

Welp — I’ve tried twice. Deleted the plugin, deleted the directory. Tried to add the plugin I d/l from the site, and got these two errors:

Warning: require_once(/home/customer/www/forwardky.com/public_html/wp-content/plugins/mc4wp-premium/vendor/autoload.php): failed to open stream: No such file or directory in /home/customer/www/forwardky.com/public_html/wp-content/plugins/mc4wp-premium/mc4wp-premium.php on line 51

Fatal error: require_once(): Failed opening required ‘/home/customer/www/forwardky.com/public_html/wp-content/plugins/mc4wp-premium/vendor/autoload.php’ (include_path=’.:/usr/local/php73/pear’) in /home/customer/www/forwardky.com/public_html/wp-content/plugins/mc4wp-premium/mc4wp-premium.php on line 51

So, at this point, not sure what to do.

Hello @bruceinlouisville,

Can you try again with the new version that just went out please, version 4.8.12?

It seems I missed something in my previous reply. Having a very shitty day. ?? Version 4.8.12 should definitely work as expected though – no doubt about it this time.

I am STILL having the issue. I’ve rename the /wp-content/plugins/mc4wp-premium/ directory, downloaded the latest from https://my.mc4wp.com/plugins and then uploaded it to my site. My site goes into recovery mode and fails with the following errors:

An error of type E_COMPILE_ERROR was caused in line 51 of the file /var/www/html/interwebz/wp-content/plugins/mc4wp-premium/mc4wp-premium.php. Error message: require_once():

Failed opening required ‘/var/www/html/interwebz/wp-content/plugins/mc4wp-premium/vendor/autoload.php’ (include_path=’.:/usr/share/php’)

Any ideas on how to fix this?

Hello @evit,

Ugh. Sorry to hear it. Can you try version 4.8.12 please? That should resolve the issue for you – I missed something in my previous reply but we’ve pushed a proper fix since then.

Hey @dvankooten,

Indeed it is now working. =) Thanks to your great work! Thanks for being so responsive and focused on your users. You ROCK!

Have a great holidays!

OK, pulled 4.8.11, installed 4.8.12. All seems working now. Thanks for the quick response!

Hi everyone,

version 4.8.12 works fine for me again. ??

Thanks for the quick solution!

Hi !
I also have this issue,and my site crashed. So I’ve rename the /wp-content/plugins/mc4wp-premium/ directory, downloaded the 4.8.12 version from https://my.mc4wp.com/plugins and then uploaded it to my site. Before I activate it, I wanted to know if I should do something with the folder I have renamed or do I simply have to activate the new version?

Thanks a lot !

Caroline

Hi @caroso73, Once you have the latest version and you verify it is working — you can then delete the old one you renamed in the /plugins directory. If you didn’t it could be a future vulnerability to leave older version of the plugin that would leave you open to getting hacked. It is good cybersecurity hygiene.

Thanks @evit !

Really appreciate your help !