Mailchimp plugin kills my PHP…

Hey aka4751,

Thanks for swinging by the forum. I certainly understand the concern over that unexpectedly high CPU usage.

One option that might help in this situation would be to dig into the code for our plugin, while commenting out some of our CSS. Fortunately, another MailChimp List Subscribe Form user that encountered a similar problem was kind enough to post a solution on their blog. In our testing, we’d also found that commenting out lines 108 and 109 (as well as 111) helped.

Here’s their blog post: http://www.limecanvas.com/how-to-stop-the-mailchimp-plugin-slowing-down-your-website/

To locate the PHP file, log into your WordPress admin panel, click Plugins, and click the Edit button next to MailChimp. From there, select the mailchimp/mailchimp.php file. From there, try commenting out the code shown here:

wp_enqueue_style('mailchimpSF_main_css', home_url('?mcsf_action=main_css&ver='.MCSF_VER));
	wp_enqueue_style('mailchimpSF_ie_css', MCSF_URL.'css/ie.css');

It may also help to try and comment out this line:
$wp_styles->add_data( 'mailchimpSF_ie_css', 'conditional', 'IE' );

This guide from the W3Schools may help with getting that commented out, should you need it:
http://www.w3schools.com/php/php_syntax.asp

However, it’s worth noting that updates to the plugin will remove the changes made to the PHP file, so it may be necessary to remove that code again in the future.

Let us know if there are any questions, or if the problem persists. We’ll be happy to help! 🙂
-mc_elliot

Hey aka4751!

It’s good to hear from you.

I totally understand the apprehension when it comes to possibly altering the underlying code. Fortunately, commenting out those 2 or 3 lines wouldn’t prevent the plugin from working. Instead, it will alter what we’d be bringing in, which should hopefully alleviate the performance issues.

That said, the change is completely reversible, if you decide it’s not wanted. The commented out code could be removed from the php file at any time, and future updates should actually remove it, regardless.

Let us know if that doesn’t quite address the problem, and we’ll be very happy to offer up some additional suggestions.

-mc_elliot

Hey Steven,

Thanks for hopping in.

I do see how it would be valuable to remove that bit of code, and we’re happy to pass that feedback along internally.

As always, feel free to post any future questions in another thread!
-mc_elliot