emcelroy

For the record, we’ve uninstalled the MailChimp for WordPress plugin and replaced it with our own custom option. So the form at the URL mentioned above works correctly now, but not because we figured out the problem with the plugin form.

Sorry, but that’s not quite right. The required attribute is only added to those fields dynamically by javascript when the “Send me the @concord newsletter by snail mail” option is selected by the user. I’ve just double checked to make sure that’s the case and it is.

By default, only the email address field has a required attribute. Here’s a screen shot of the form code on the MailChimp for WP > Forms page: https://staff.concord.org/~emcelroy/fields.png

There is no required attribute for the first or last names fields appearing there, nor do they have a required attribute when you initially load our public subscribe page. The same is true of the address fields — no required attribute is present by default.

I tried removing the javascript that dynamically adds the required attribute to the name and address fields to see if that was somehow causing the problem, but removing it has no effect on this problem. The form still considers the mailing address fields as required.

Notice too in the screen shot how the mailing address items in the “Choose a field to add to the form” are marked with red asterisks. As I understand it, this means the plugin thinks those fields are required. Is that correct? In my local copy of the site where the form works as expected, those items are _not_ marked with a red asterisk.

Sure. You can see a screenshot at https://staff.concord.org/~emcelroy/list-field-settings.png

I seem to have found a solution.

I had been using our Google API “Key for server apps” with the blog site’s IP address listed as an allowed IP in the plugin’s settings. Just now, I tried entering our Google API “Key for browser apps”, and the plugin started working again.

Thanks for the suggestion, but it didn’t help.