Mailchimp List Subscribe Form
| 开发者 | Mailchimp |
|---|---|
| 更新时间 | 2024年11月12日 23:29 |
| WordPress版本: | 6.7 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
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.
安装:
This section describes how to install the plugin and get started using it.
Version 2.8+
- Unzip our archive and upload the entire mailchimp directory to your
/wp-content/plugins/ directory. - Activate the plugin through the Plugins menu in WordPress.
- Navigate to the Mailchimp menu.
- Click the Log in button and proceed through the OAuth flow, logging in to your Mailchimp account and authorizing the application.
- Select the list where you want to send new Mailchimp subscribers.
- Optional: Turn Merge Fields and Groups on or off. Navigate to Appearance, and click Widgets. Drag the Mailchimp Widget into one of your Widget Areas.
- Optional: adjust frontend site display with available CSS options.
屏幕截图:
常见问题:
Can I have multiple forms on one page?
No, only one form should exist per page, no matter the display type (block, widget, or shortcode).
Why am I not seeing all my fields in my form?
You need to ensure that the fields are enabled both in your Mailchimp account (Audience > Signup forms) and in the settings of this plugin. Once the fields are enabled in both places, then they'll appear in the editor and frontend of your site.
How can I translate “MailChimp List Subscribe Form”?
Internationalization (i18n) is available on GlotPress at https://translate.wordpress.org/projects/wp-plugins/mailchimp/. Any assistance translating the plugin is greatly appreciated!
更新日志:
1.6.2 - 2024-11-12
Note that this release bumps the WordPress minimum version from 6.1 to 6.3.
- Changed: Bump WordPress "tested up to" version 6.7 (props @qasumitbagthariya, @vikrampm1, @dkotter via #71).
- Changed: Bump WordPress minimum supported version from 6.1 to 6.3 (props @qasumitbagthariya, @vikrampm1, @dkotter via #71).
- Fixed: Ensure the field name is properly added to the error message when the email address is blank (props @iamdharmesh, @jerclarke, @dkotter via #74).
- Changed: Improved migration flow from API Key to OAuth authentication for a better user experience (props @iamdharmesh, @jeffpaul, @dkotter, @qasumitbagthariya via #67).
- Changed: Updated the menu SVG icon (props @dkotter, @jeffpaul via #65).
- Fixed: Ensure that the settings remain persistent between logging out of the account and logging in again (props @iamdharmesh, @jeffpaul, @dkotter, @qasumitbagthariya via #66).
- Security: Bump
serve-staticfrom 1.15.0 to 1.16.2 andexpressfrom 4.19.2 to 4.21.0 (props @dependabot, @dkotter via #55). - Security: Bump
webpackfrom 5.91.0 to 5.94.0 (props @dependabot, @dkotter via #59).
- Added: Mailchimp List Subscribe Form custom block (props @nateconley, @dkotter, @jeffpaul via #35, #38).
- Added: PHP 8.3 compatibility and minimum PHP version of 7.0 (props @nateconley, @jeffpaul, @dkotter via #26).
- Added: WordPress 6.5 compatibility (props @nateconley, @dkotter, @jeffpaul via #27).
- Added: OAuth authentication for connecting a Mailchimp account with WordPress (props @iamdharmesh, @dkotter, @jeffpaul via #47, #48, #50, #52).
- Added: New user signup flow, allowing users to sign up for a Mailchimp account from within the plugin (props @iamdharmesh, @dkotter, @jeffpaul via #51).
- Added: Created a
LICENSE.mdfile and sets the license in the plugin toGPL-2.0-or-later(props @jeffpaul, @dkotter via #14). - Added: Plugin icon and banner assets (props @eddieshrake, @jeffpaul, @dkotter via #28).
- Changed: Bump WordPress "tested up to" version 6.6 (props @qasumitbagthariya, @vikrampm1, @jeffpaul via #43).
- Changed: Ensure the signup form is only visible when a list is selected in the settings (props @iamdharmesh, @dkotter, @qasumitbagthariya via #54).
- Changed: Moved settings page and link to top-level WP Admin menu item (props @nateconley, @dkotter, @jeffpaul via #29, #33).
- Changed: Admin styles to match updated Mailchimp brand guidelines (props @nateconley, @dkotter, @jeffpaul, @eddieshrake via #31).
- Changed: Replaced references of MailChimp to Mailchimp except where those references are explicitly functional code (to limit the additional class/function updates needed) (props @jeffpaul, @dkotter via #14).
- Changed: Updated
readme.txtandmailchimp.phpheader values to the WP.org standards (props @jeffpaul, @dkotter via #14). - Changed: Moved screenshots into a new
.wordpress-orgdirectory (props @jeffpaul, @dkotter via #14). - Changed: Moved translations to GlotPress (props @nateconley, @dkotter, @jeffpaul via #39).
- Deprecated: Function
mailchimpSF_signup_formdeprecated in favor ofmailchimp_sf_signup_form(props @nateconley, @dkotter via #24). - Deprecated: jQuery scrollTo (props @nateconley, @dkotter, @jeffpaul via #27).
- Removed: Support for WordPress < 6.1.1 (props @nateconley, @dkotter, @jeffpaul via #27).
- Removed: Polyfills for WordPress < 2.8.0 (props @nateconley, @dkotter, @jeffpaul via #27).
- Removed: Monkey Rewards integration (props @nateconley, @dkotter, @jeffpaul via #30).
- Removed: IE-specific admin stylesheet (props @nateconley, @dkotter, @jeffpaul, @eddieshrake via #31).
- Fixed: Formatting from linting checks (props @nateconley, @dkotter via #23).
- Fixed: Datepicker display on frontend (props @nateconley, @dkotter, @jeffpaul via #25).
- Fixed: Accessibility for admin settings page (props @nateconley, @dkotter, @jeffpaul, @eddieshrake via #31).
- Fixed: Properly handle the scenario where a non-valid list is updated (props @dkotter, @qasumitbagthariya, @nateconley, @vikrampm1 via #40).
- Fixed: Ensure the custom block and shortcode both have consistent spacing (props @dkotter, @qasumitbagthariya, @nateconley, @vikrampm1 via #41).
- Fixed: Address some PHP warnings when a form submission happens (props @iamdharmesh, @dkotter, @qasumitbagthariya via #54).
- Changed: Updated
readme.txtlink. - *Fixed: PHP warning for merge tags.
- Fixed: Double slashes on resources being loaded. View historical changelog details here.