jason_lane

@msdeadlines – It turns out I had the same permissions problem, but I hadn’t noticed (didn’t actually trying clicking on the Mailchimp Settings). Anyway, I found the fix to that one, too. The Mailchimp plugin is checking for user capability ‘edit_plugins’, which seems logical, but it turns out that the ‘edit_plugins’ cap can be switched off globally by the command:

define( 'DISALLOW_FILE_EDIT', true );

In my case, I am using the “Better WP Security Plugin” and have ticked the option to “Turn off file editor in WordPress Back-end.” which means admins no longer have the ‘edit_plugins’ capability, and therefore the Mailchimp settings page doesn’t let them in. You may have a similar security plugin installed, or even a theme that is disabling the file editor. The quick fix is to change the defined cap on line 31 of mailchimp.php:

define('MCSF_CAP_THRESHOLD', 'edit_plugins');

I usually use ‘manage_options’ on my plugins. Once you’re able to get to the settings page, you may just need to check that everything is configured correctly, and hopefully your form submission problem will get fixed. Based on the error you posted, it sounds like something to do with your Interest Groups settings.

For extra information about the ‘edit_plugins’ cap issue:

https://www.ads-software.com/support/topic/edit_plugins-capability?replies=2

https://sltaylor.co.uk/blog/wordpress-edit_plugins-capability/

@mc_nate

The bug is on line 71 in mailchimp.php

The existing code is:

add_filter('plugin_action_links', 'mailchimpSD_plugin_action_links', 10, 1);

This should be changed to something like the following (works for me):

add_filter('plugin_action_links_' . plugin_basename( __FILE__ ), 'mailchimpSD_plugin_action_links', 10, 1);

I ran across this problem and found that this has been discussed in the WP bug tracking system. There is a suggested solution that plugin developers should follow, and you can easily implement the fix yourself if you know a little PHP. See the thread here: https://core.trac.www.ads-software.com/ticket/6453 (The fix is in comment #11)

This is actually a Facebook bug, not a problem with the plugin. See here:

https://bugs.developers.facebook.net/show_bug.cgi?id=15200

According to that page, the bug is supposed to be fixed now (since March 14 2011). Are your tabs now working properly from https?