Mailchimp for WordPress

New in 4.12.6: accessibility and reliability improvements

Published on by

Version 4.12.6, released yesterday, is a smaller release than 4.12.2, but still worth highlighting. It improves accessibility of generated form fields and makes background sign-up processing more reliable. It also tightens up validation and logging in a few places.

More accessible generated fields

When you use the field generator in the form editor, the plugin now creates markup that better associates labels with their inputs. Checkbox and radio fields are grouped in a fieldset, and inputs are wrapped by their labels where appropriate.

This makes the generated forms easier to understand for screen readers and other assistive technology. Existing forms will keep working as before, but new fields generated by the plugin will use the improved markup.

The Premium Styles Builder was updated alongside this change so its generated CSS works correctly with both the old and new form markup.

More reliable integration sign-ups

Since version 4.12.3, sign-ups coming from integrations such as WooCommerce, Contact Form 7, or other supported plugins are processed in the background through WordPress cron. This helps avoid slowing down the original form submission or checkout request while the plugin talks to Mailchimp.

Version 4.12.6 fixes an issue where some runtime options, such as double opt-in for the Ninja Forms integration, could be lost during that background step. Thanks to Jon Parker for reporting this and providing a patch.

Site Tracking Pixel refinements

We also continued improving the Mailchimp Site Tracking Pixel support introduced earlier this year. The plugin now automatically discovers or registers your site in Mailchimp when you enable the feature, so there is less manual setup involved.

In yesterday’s release, we fixed an issue where disabling the Site Tracking Pixel setting was not always saved correctly. Premium users will also notice that the e-commerce tracking pixel handling has moved into the free plugin, so the feature is managed in one place.

Safer validation and logging

This release also includes a few defensive improvements that should mostly stay invisible during normal use:

  • Submitted form data is now sanitized more consistently and field lengths are capped.
  • Email address validation no longer relies solely on WordPress core’s is_email() function.
  • Debug log messages are truncated if they are unusually large.
  • Email addresses in debug logs are obfuscated more carefully.

These changes are mostly about keeping edge cases contained: unusually large submissions, unexpected field names, or log messages that could become noisy or expose more information than needed.

Thanks to Jack Feldcher for reporting the email obfuscation and oversized input issues that prompted these improvements.

Premium changes

Mailchimp for WordPress Premium also received a few related updates over the same period. Logging now defaults to the table overview and only shows integrations that are installed or have entries. There is also a new setting to disable logging entirely.

The e-commerce code now avoids a full order save when only updating metadata, which prevents a potential loop in some WooCommerce setups. Deferred scripts now use WordPress’ script loading strategies where possible.

Updating

You can update Mailchimp for WordPress from the Plugins screen in your WordPress admin area, or download the latest version from WordPress.org.

As always, if something does not work as expected after updating, please let us know.