Log vs Mailchimp List Subscribe Form

Log emails to the WordPress database for later analysis. Access is restricted to administrators, and emails with WordPress passwords are obfuscated for security / privacy. Useful for diagnosing lost email problems. Use this plugin with Disable Emails to divert all WordPress emails into logs, especially handy for developers. Logs are automatically purged after a defined period, set through a settings page in the WordPress admin. Setting the period to 0 prevents logs from being purged. Uninstalling the plugin purges all logs. Translations Many thanks to the generous efforts of our translators: Czech (cs-CZ) — Rudolf Klusal English (en-CA) — the English (Canadian) translation team English (en-GB) — the English (British) translation team French (fr-FR) — Hugo Catellier Korean (ko-KR) — the Korean translation team Russian (ru) — the Russian translation team If you’d like to help out by translating this plugin, please sign up for an account and dig in.

Use the Mailchimp List Subscribe plugin to quickly add a Mailchimp signup form block, widget, or shortcode to your WordPress site. After installation, if you already have a Mailchimp account, you’ll log in with that account and then proceed to configure settings. If you don’t have an account, you can create one directly in the plugin. After entering in all your personal details, you’ll need to activate your account via an email that will be sent to you. Once done, you’ll proceed to configure settings. On the settings screen, you’ll select your Mailchimp list, choose merge fields and groups, and configure other options. Once done, you can now add the block, widget, or shortcode ([mailchimpsf_form]) to your site. Typically, installation and setup will take about 5-10 minutes, and absolutely everything can be done via the WordPress Setting GUI, with no file editing at all. WordPress.com compatibility is limited to Business tier users only. How to add a signup form if you have a WordPress.com site. Access Token Encryption Starting in version 1.6.0, authentication has changed to use OAuth. As part of this process, we retrieve an access token that can be used to make API requests. To provide a high-level of security, this access token is encrypted before being stored in the WordPress database. In order to ensure this access token can be decrypted when used, the plugin relies on certain security constants that should remain unchanged. With no additional configuration, we use the standard LOGGED_IN_KEY and LOGGED_IN_SALT constants that are normally set in your site’s wp-config.php file. Some sites make use of security plugins that rotate these constants on a periodic basis. When this happens, we won’t be able to decrypt the access token and you’ll need to reconnect your Mailchimp account to generate a new access token. To prevent such issues, it is recommended to define two additional constants in your site’s wp-config.php file: MAILCHIMP_SF_ENCRYPTION_KEY and MAILCHIMP_SF_ENCRYPTION_SALT. These constants should consist of a combination of characters, preferably at least 32 characters long. Once set, these values should not be changed. For strong values, you can copy some of the values from here and use them. You’ll end up with additional code like the following in your wp-config.php file: define( 'MAILCHIMP_SF_ENCRYPTION_KEY', 'put your unique phrase here' ); define( 'MAILCHIMP_SF_ENCRYPTION_SALT', 'put your unique phrase here' ); If these constants are added after you’ve already authenticated with Mailchimp, you will need to reconnect your account. To avoid this, you can copy the values from LOGGED_IN_KEY and LOGGED_IN_SALT (if they exist) to MAILCHIMP_SF_ENCRYPTION_KEY and MAILCHIMP_SF_ENCRYPTION_SALT respectively. Upgrading If you are upgrading to version 1.2.1 and you used the widget in your sidebar previously, all you need to do is drag the Mailchimp Widget back into the sidebar, visit the Mailchimp settings page (which will have maintained your prior settings), click the “Update List” button, and you’re done!