mc_jesse

You should not do that. That is name-spaced for our plugin to prevent conflicts with other plugins using varying versions of our API wrapper.

If you are interested in writing a plugin that uses our API, you should:

• download a fresh copy of the PHP wrapper
• check out the example code that comes with the wrapper
• refer to the API documentation if something’s not clear
• Post API-related questions if the docs don’t settle it
• finally, namespace the wrapper for your plugin

It’s certainly not our plugin doing that. You’ll need to work out whatever the plugin and/or javascript conflict that’s occurring on your side by adding/removing/enabling/disabling things until you track it down.

The first thing to do is answer the question I asked above:

What version of PHP are you running (full version, so 5.1.4, not 5 or 5.1)?

Just tested that combo and it is working fine together. What version of PHP are you running (full version, so 5.1.4, not 5 or 5.1)?

Have you clicked the link in the confirmation emails sent? I’d guess not.

Not at this time.

Did you try following the upgrade instructions?

@chace the issue is related to having “(” and “)” in the group name. Removing them from the mailchimp side and then updating the list in the plugin settings will make it work immediately. We’ll look at a more robust fix.

@mehuljk that’s not actually a related need. Currently the plugin only support the first set of interest groups on your list.

Not using the plugin. You can try using the embed code for your list.

Did you upgrade the plugin at some point there? And if so, did you try following the upgrade instructions?

Sounds like you changed your list on the MC side and didn’t update the settings for your list in the plugin. Go there and click “update list”, then try again.

That’s not our plugin/widget – you’ll be better off going to the page for the plugin you have installed and follow the “forum” link there.

I understand what you are being told, but from a technical standpoint that’s useless. If a host has actually given a technical description of the issue we’d have something to at least consider.

That’s not the “ver” parameter that we’re setting – looks like WordPress is changing it and even if we use a different named parameter, it still appends the version number. I’ll take a look, but since it’s not something we’re doing, it’s not going to be real high on the list.

The current version (1.2.2) or something else? How did it crash? What errors did you see? Are you actually running WP 3.0.5?