mc_jesse

If we put it in a separate file, it is still going to get overwritten when the plugin is upgraded. If you need separate css, turn off our “custom styling” option and then add whatever you need to one of your existing css files.

Sounds like it is the theme, then. I’d guess they are applying something to label tags in sidebar widgets. Without changing themes, the best you can do is try overriding whatever it is doing after the theme’s css is included.

The CSS you have here isn’t going to apply much of anything to the form. Assuming you actually have css rules correctly setup somewhere, take a look at the source of the generated page and see where your styles are being pulled in. Just make sure that anything the plugin emits is before them.

Have you tried turning off the “custom styling” option in the plugin setup?

Did you make sure the custom styling option was turned off?

Talk to you host or server admin about enabling SSL support for PHP.

If you can post errors from your Apache or PHP error logs there’s a chance that we might be able to troubleshoot without looking at their plugin.

However, since it is not a free plugin that we can get and test without paying, I’d suggest reporting this to them. Hopefully they’ll be willing to test it and either fix their side or suggest to us where the conflict is coming from. If you do that, I’d also suggest giving them the link to this thread.

Aside from leaving a comment, no, not that I’m aware of.

The new version is available, so give it a shot.

That was a great hint for me – the code verifying the API Key, which I assumed was working, was not. It has been updated and should be available in the next 10 – 15 minutes. Of course, just grabbing the proper api key will work as well.

Look for v1.1.14 today. That should fix the issue.

I’ll go ahead and warn you – v1.1.14 will be available shortly and most or all of the padding and margins have been removed. The widths we have set now are there to deal with themes that use floats by default.

If/when you upgrade, I’d be interest in any feedback.

I did, and I’ve been trying to test various versions of the css we’re using to have it not break for others when we push a new version since none of the themes we tried it with experienced the problem you all are reporting.

That said, hopefully it will be out today or tomorrow.

We’ve slowly been working towards that, but have also taken steps back.

The problem we have is balancing between people who can actually style things and those who can’t (who appear to be the vast majority). More than likely we’ll have to look at being much more blunt with basic styles included when styling is turned off.

Unfortunately, no. However that’s only because we haven’t been able to replicate the problem and details from folks having it have been scarce. I suspect there’s a conflict somewhere – if you could post your version of WordPress and the plugins installed, we might have some luck tracking it down.

The required field asterisk is now wrapper in a span tag with a class of “mc_required”.

There are no plans at this time to build the image upload feature you’ve mentioned. As far as I know, though, you should be able to add your own css to style the button using an image.