外掛說明
Forward: Simple Mailchimp Form adds a lightweight signup form that subscribes visitors to a Mailchimp audience. Configure your API key, default audience/list ID, subscription status, and response messages, then place the form with a shortcode.
The plugin is intentionally small: it focuses on one form, one audience/list, and clear setup.
Key features
- Adds a Mailchimp signup form with
[simple_mailchimp]. - Collects email address, first name, and last name.
- Supports immediate subscription or confirmation by email.
- Lets you customize success and error messages.
- Uses the WordPress HTTP API for Mailchimp requests.
- Includes bundled translation files for common languages.
Requirements
- A Mailchimp account.
- A Mailchimp API key.
- A Mailchimp audience/list ID.
Accessibility
WCAG 2.2 Level AA compliance is a release requirement for the interfaces generated by Forward: Simple Mailchimp Form. The settings screen and signup form are tested for labels and accessible names, keyboard operation, visible focus, contrast, reflow, target size, input purpose, unique identifiers, and announced success or error messages.
The active theme, custom CSS, customized response text, embedded page content, and Mailchimp’s external confirmation experience can affect end-to-end WCAG conformance.
Shortcode and template usage
Add the form to a post, page, or widget area with:
[simple_mailchimp]
Add the form from a theme template with:
<?php echo do_shortcode( '[simple_mailchimp]' ); ?>
The settings screen also includes the generated HTML form markup if you want to adapt the fields manually.
External service and privacy
This plugin connects to the Mailchimp API when a visitor submits the signup form.
Submitted email address, first name, last name, the configured subscription status, and the configured audience/list ID are sent to Mailchimp over HTTPS. The API endpoint is based on your API key’s data center and uses this pattern:
https://<dc>.api.mailchimp.com/3.0/lists/{list_id}/members/{subscriber_hash}
The plugin stores the API key, default list ID, subscription status, and response messages in WordPress options. It does not store submitted subscribers in WordPress.
Mailchimp’s terms and privacy information are available at https://mailchimp.com/legal/terms/ and https://mailchimp.com/legal/privacy/.
螢幕擷圖
安裝方式
- Install the plugin from Plugins > Add New, or upload the
simple-mailchimpfolder to/wp-content/plugins/. - Activate the plugin from the Plugins screen in WordPress.
- Open Settings > Forward: Simple Mailchimp Form.
- Enter your Mailchimp API key and default audience/list ID.
- Choose whether new subscribers are added immediately or confirmed by email.
- Add
[simple_mailchimp]to any post or page.
常見問題集
-
Do I need a Mailchimp account?
-
Yes. The plugin sends subscribers to Mailchimp, so you need a Mailchimp API key and audience/list ID.
-
Where do I find my Mailchimp list ID?
-
In Mailchimp, open the audience you want to use and copy its audience/list ID from the audience settings.
-
Can I use the form in a template file?
-
Yes. Use
do_shortcode( '[simple_mailchimp]' )from your template. -
Does the plugin store subscribers in WordPress?
-
No. Subscriber details are sent to Mailchimp and are not stored locally by this plugin.
使用者評論
這個外掛目前沒有任何使用者評論。
參與者及開發者
變更記錄
1.2.19
- Keep focused subscriber-status selects readable in dark mode.
- Associate success, error, and retained field values with only the submitted form when a page contains multiple shortcodes, and give response panels reliable contrast.
1.2.18
- Add Danish translation for the descriptive new-tab link text.
1.2.17
- Add the WCAG 2.2 AA release gate and accessibility documentation.
- Generate unique form control IDs when the shortcode appears more than once.
- Add input-purpose autocomplete tokens and announced success or error messages.
- Improve hover and focus contrast in the form and settings interface.
1.2.16
- Refresh the WordPress.org screenshot gallery with clearer, English, outcome-led examples.
1.2.15
- Confirm compatibility with WordPress 7.1.
1.2.14
- Add a responsive More Forward plugins teaser section with plugin icons to the settings screen.
1.2.13
- Add translated setup help for Mailchimp API keys and audience IDs.
- Move settings screen styles into an enqueued admin stylesheet for cleaner WordPress.org checks.
1.2.12
- Remove the legacy manual textdomain loader so WordPress.org can load translations automatically without Plugin Check warnings.
1.2.11
- Improve shortcode form target sizes, focus styles, and scoped front-end styling for accessibility.
- Improve target sizing for the custom HTML details control on the settings screen.
1.2.10
- Apply the Forward color palette to the settings and help screens, including light and dark color modes.
- Prefix internal shortcode helper functions for cleaner WordPress Plugin Check results.
1.2.9
- Fix front-end form submission processing so nonce validation runs after WordPress has loaded its pluggable functions.
- Improve settings labels for the customizable success and error messages.
1.2.8
- Improve responsive behavior for the settings and help screen on narrow admin viewports.
1.2.7
- Only repopulate submitted form fields after nonce validation to satisfy Plugin Check form handling requirements.
1.2.6
- Correct the Forlæns author URL to
forlaens.com.
1.2.5
- Add the shared Forward icon to plugin assets and the settings screen.
1.2.4
- Refresh the settings and help screens with a cleaner, modern WordPress admin layout.
- Add a clearer saved-settings notice.
1.2.3
- Add bundled translations for common languages.
- Improve settings security with capability checks, nonces, sanitization, and safe redirects.
- Add frontend nonce verification for form submissions.
- Use the WordPress HTTP API for Mailchimp requests with standard TLS verification.
- Always subscribe to the configured default list instead of accepting a submitted list ID.
- Add browser-side required fields to the signup form.
- Fix uninstall cleanup for plugin options.
- Remove donation prompts from the plugin screen and readme.
- Remove obsolete direct-access messaging and unnecessary output buffering.