mc_gabe

Hey Aaron,

Thanks for getting in touch. We definitely want to help however we can here. In order to do so, it’d be a great help if you could provide us with a bit more information about your environment so we can track the issue and investigate.

We’re looking for information like the following:

• Version of plugin (It sounds like you’re using 1.3. Is that correct?)
• Version of WordPress (You already mentioned 3.7.1)
• Web Host
• Are you seeing this issue in just one browser or in multiple browsers?
• Does the issue persist if you clear your cache and cookies in a browser you’re seeing this issue pop up in?

Additionally, are you able to check with your host to see if any traffic is being blocked on the installation?

It could also be an issue with a conflict with a plugin or theme. A way to troubleshoot this would be to try temporarily deactivating all plugins on the site, then enabling the MailChimp plugin and seeing if you can connect.

We look forward to hearing back!
-Gabe

Hey David,

Thanks for writing to us. We’re happy to help however we can. Can you provide us a bit more detail so we can look into things for you?

Can you give us the following details?

• Version of our plugin
• Version of WordPress
• Your web host
• Which particular step in using MailChimp appears to be failing? What piece of functionality are you trying to get working when you see that error?

That additional information can help us out quite a bit.
Thanks,
Gabe

Hey Stefan,

Thanks for creating this new topic. We are trying to track this issue at the moment to see any commonalities we might be able to between situations which appear to be similar. In order to do this, we want to collect as much information as possible. Can you give this consolidated information here in this thread?

Things like:

• Version of plugin
• Version of WordPress
• Host
• Which particular step in using MailChimp appears to be failing. What piece of data are you having issues getting?
• What message (if any) are you getting?

It sounds as if your host (which was mentioned as being the same as a host in the previous thread) may be blocking some ingoing or outgoing traffic to MailChimp’s servers, so checking with your host about potential ports or traffic being blocked, thereby disrupting standard functionality.

We appreciate any details you can provide.
-Gabe

Thanks for getting back to us. At this point this does appear to be a bug, so we’re treating it as such with a ticket open for correcting this behavior in a future release. There isn’t currently something to be done on the user’s end to solve the issue. We definitely appreciate your understanding while our developers work on that.

-Gabe

Hey Chris!

Thanks for getting in touch. I took a look at your site in order to see what’s up, but the text field for email address under Email Option #2 looked pretty normal to me. Are you still seeing this issue? If so, can you tell us a bit about the environment you’re seeing this in? Are you seeing this in a particular browser or multiple browsers? On just one computer or on multiple devices?

If you’re still seeing this problem, we’ll be happy to take a look with a bit more information for determining how to test.

Thanks,
Gabe

Hey there!

Thanks for writing in. Localhost operation of the plugin isn’t currently supported with this plugin. We do know this is something some are looking for and take your desire for this seriously.

If you have any other questions, please let us know.

Thanks,
Gabe

Hey there!

Thanks for writing in to us here. I took a look at your form on your site and I see what you mean. While the options under “Custom Styling” in the plugin settings are limited to the area below the plugin’s header, you could disable the custom styling section and instead applying the border and background formatting you’d like to the entire widget container.

In the Plugin Settings screen, if you scroll down to the CSS Cheat Sheet, you’ll see this class as the one used for formatting the whole container: .widget_mailchimpsf_widget

Adding some styling in your site’s CSS for the .widget_mailchimpsf_widget class should do the trick.

-Gabe

Hey there!

Thanks for posting in here for help. I’ve taken a look at both forms. To start, I’m actually seeing the rollover appear to work on your website. Is that still an issue for you? If so, is it an issue across browsers?

For the required field in the plugin, we’ve noticed the same behavior you’re discussing with required fields of the “phone number” type. I’ve passed that on for you to be looked at by the developers for a potential fix.

If we can help with any other information, please let us know.

-Gabe

Hey Trine,

After taking a look at your site, it looks like we may need some clarification on what you (and foxandq, of course) are looking to specifically change. If you’re talking about the background of the input fields themselves, you can try adding
background-color: rgba(255,255,255,0.1)
to the CSS for .mc_input. The last value can be altered up to 1 and down to 0 to change how transparent the background should be and the first three numbers can be altered to change the color itself.

It’s possible for a WordPress theme to have styles for input areas overriding MailChimp’s .mc_input class, in which case the aforementioned background-color change would also have to be applied there.

If the desire for a transparent background is on some element, though, can you tell us what that is?

Thanks.

If the widget isn’t appearing as an option at all, that could indicate the plugin has been deactivated for some reason. If you head to the WordPress Admin area, then go to Plugins > Installed Plugins, is the MailChimp plugin currently active? If it’s been deactivated, then activating it again from there should bring the widget back under Appearance > Widgets.

Hey Praveen,

There may be a couple of different solutions here depending on what the issue you’d like to solve is.
First, you could try adding media queries to the plugin’s CSS in order to get the particular CSS to only load for devices or display areas above a certain width. (using min-width or min-device-width).

Alternately, you could try adding javascript conditionals within the plugin’s code around to check for desired screen sizes, and only then apply the in-page CSSor call the external CSS files in the event the size condition is met.

We may be able to help a bit more if you can elaborate on what particular issues you have with the current behavior. If you have a link we can check out and what particular behavior you’re trying to avoid, we may be able to dig a bit deeper for you.