Mailfix Contact Forms
| 开发者 | mailfix |
|---|---|
| 更新时间 | 2026年6月15日 07:48 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Mailfix Contact Forms adds a WordPress-native contact form builder with saved submissions, notification emails, spam protection, and a clear admin workflow.
Watch a short overview of Mailfix Contact Forms:
https://www.youtube.com/watch?v=4jTuRyrO8W0
Main features:
- Form field builder with live appearance preview.
- AJAX form submissions.
- Gutenberg block for inserting forms.
- Stored messages with unread/read, archive, and trash views.
- Admin email notifications and optional thank-you emails.
- GDPR/privacy consent checkbox with editable text and privacy policy link.
- HTML email templates with editable content.
- Mail logs with readable HTML previews.
- Custom SMTP settings for better deliverability.
- Honeypot protection, minimum submit time, rate limiting, optional Google reCAPTCHA v3, and blocked spam counters.
- CSV export for one form or all forms.
- Form appearance controls, including colors, field size, button alignment, and border radius.
安装:
- Upload the plugin folder to
/wp-content/plugins/or install it through the WordPress admin. - Activate the plugin from the Plugins screen.
- Open
Formsin the admin and create a new form. - Copy the shortcode from the form editor.
- Insert the shortcode into a page, post, or compatible page builder.
屏幕截图:
常见问题:
Does the plugin send data outside my website?
By default, no. Submitted messages are stored locally in the WordPress database and emails are sent through wp_mail() or your configured SMTP server. If Google reCAPTCHA v3 is enabled, the reCAPTCHA token is verified through Google reCAPTCHA.
How do I insert a form into a page?
Copy the shortcode from the form editor, for example [mailfix_form id="123"], and paste it into a page, post, or compatible builder.
Where do I configure email notifications?
Open Forms > Notifications, choose a form, and configure recipients, sender details, the admin notification, and the optional thank-you email.
What personal data does the plugin store?
The plugin stores submitted form fields, submission date, an IP hash, and the user agent for administration and basic security checks. The IP hash is not a readable IP address. If Google reCAPTCHA v3 is enabled, the verification token is checked through Google reCAPTCHA.
How can I test email delivery?
Open Forms > Notifications, choose a form, and send a test email. The result is stored in the mail log. A sent status means WordPress accepted the email for sending; actual delivery still depends on the mail server and domain DNS.
Does the form work without JavaScript?
Frontend submissions are designed as AJAX forms and require JavaScript in the visitor's browser.
更新日志:
1.1.51
- Fixed default form field labels so they are not saved in the admin language.
- Fixed admin font scoping on the Forms screen.
- Updated Mailfix styles to inherit fonts instead of defining a custom font stack.
- Added a short overview video to the plugin readme.
- Updated Mailfix Pro links to use the English Pro page outside Czech admin locales.
- Added a dismissible WordPress.org review banner on the plugin dashboard after initial use.
- Removed unused helper methods and stale admin CSS selectors.
- Fixed field radius consistency across frontend, form preview, and choice fields.
- Added an appearance option to show or hide the form title.
- Improved sticky preview behavior when editing appearance settings on new forms.
- Added shortcode copying to the forms list table.
- Improved the form editor layout so appearance settings stay closer to the live preview.
- Reviewed WordPress.org guideline wording and clarified that the free plugin is fully functional on its own.
- Shortened older changelog entries for a cleaner WordPress.org readme.
- Protected automatic message read-state changes with a nonce.
- Hardened reCAPTCHA response handling and duplicate form redirects.
- Tightened request handling for admin notices, notification settings, SMTP tests, and frontend submissions.
- Sanitized local request arrays before passing them into internal helpers.
- Sanitized structured form editor settings before extension filters run.
- Escaped custom field HTML returned by extension filters with a strict allowlist.
- Passed sanitized email preview context to extension filters.
- Reworked message and mail log list queries to avoid dynamically interpolated SQL fragments.
- Reworked setup wizard shortcode detection to avoid interpolated IN placeholders.
- Tightened sanitization for submitted field values, SMTP/reCAPTCHA settings, and onboarding redirects.
- Improved translation cleanup and clarified rate-limit help text.
- Rechecked custom SQL reads and raised the minimum WordPress version to 6.2.
- Refined extension hooks for external add-ons.
- Rechecked message, log, dashboard, and CSV database reads.
- Cleaned package contents and prepared SQL reads.
- Added a shortcode copy box below the Publish panel.
- Standardized the public plugin brand spelling.
- Fixed notification preview compatibility and Czech translations.
- Cleaned stale translation strings.
- Renamed the plugin, aligned the text domain, and documented Google reCAPTCHA.
- Improved Gutenberg block controls.
- Split editor, frontend, notification, onboarding, message, settings, and admin action code into focused traits.
- Split SMTP handling and CSV export into dedicated classes.
- Hardened frontend option validation and proxy IP handling.
- Refined Plugin Check annotations for mail log queries.