Form appearance controls, including colors, field size, button alignment, and border radius.<\/li>\n<\/ul>\n\nAdditional features are available in a separate Mailfix Pro add-on from mailfix.cz. This WordPress.org plugin is fully functional on its own.<\/p>\n\n
External services<\/h3>\n\nGoogle reCAPTCHA<\/h4>\n\n
This plugin can optionally use Google reCAPTCHA v3 for spam protection when the site administrator enables reCAPTCHA and enters Google reCAPTCHA keys in the plugin settings.<\/p>\n\n
When reCAPTCHA is enabled for a form, the plugin loads the Google reCAPTCHA script from www.google.com<\/code> on pages where that form is displayed. When a visitor submits the form, the plugin sends the reCAPTCHA response token, the configured secret key, and the visitor IP address to Google's siteverify<\/code> endpoint to validate the submission. The plugin also offers an administrator-only secret key check that sends the configured secret key and a test response token to Google.<\/p>\n\nGoogle reCAPTCHA is provided by Google LLC. Terms: https:\/\/policies.google.com\/terms Privacy Policy: https:\/\/policies.google.com\/privacy<\/p>\n\n\n
\n- Upload the plugin folder to
\/wp-content\/plugins\/<\/code> or install it through the WordPress admin.<\/li>\n- Activate the plugin from the Plugins screen.<\/li>\n
- Open
Forms<\/code> in the admin and create a new form.<\/li>\n- Copy the shortcode from the form editor.<\/li>\n
- Insert the shortcode into a page, post, or compatible page builder.<\/li>\n<\/ol>\n\n\n
\nDoes the plugin send data outside my website?<\/h3><\/dt>\nBy default, no. Submitted messages are stored locally in the WordPress database and emails are sent through wp_mail()<\/code> or your configured SMTP server. If Google reCAPTCHA v3 is enabled, the reCAPTCHA token is verified through Google reCAPTCHA.<\/p><\/dd>\nHow do I insert a form into a page?<\/h3><\/dt>\nCopy the shortcode from the form editor, for example [mailfix_form id=\"123\"]<\/code>, and paste it into a page, post, or compatible builder.<\/p><\/dd>\nWhere do I configure email notifications?<\/h3><\/dt>\nOpen Forms > Notifications<\/code>, choose a form, and configure recipients, sender details, the admin notification, and the optional thank-you email.<\/p><\/dd>\nWhat personal data does the plugin store?<\/h3><\/dt>\nThe 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.<\/p><\/dd>\n
How can I test email delivery?<\/h3><\/dt>\nOpen Forms > Notifications<\/code>, choose a form, and send a test email. The result is stored in the mail log. A sent<\/code> status means WordPress accepted the email for sending; actual delivery still depends on the mail server and domain DNS.<\/p><\/dd>\nDoes the form work without JavaScript?<\/h3><\/dt>\nFrontend submissions are designed as AJAX forms and require JavaScript in the visitor's browser.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.1.45<\/h4>\n\n\n- Removed unused helper methods and stale admin CSS selectors.<\/li>\n<\/ul>\n\n
1.1.44<\/h4>\n\n\n- Fixed field radius consistency across frontend, form preview, and choice fields.<\/li>\n<\/ul>\n\n
1.1.43<\/h4>\n\n\n- Added an appearance option to show or hide the form title.<\/li>\n<\/ul>\n\n
1.1.42<\/h4>\n\n\n- Improved sticky preview behavior when editing appearance settings on new forms.<\/li>\n<\/ul>\n\n
1.1.41<\/h4>\n\n\n- Added shortcode copying to the forms list table.<\/li>\n
- Improved the form editor layout so appearance settings stay closer to the live preview.<\/li>\n<\/ul>\n\n
1.1.40<\/h4>\n\n\n- Reviewed WordPress.org guideline wording and clarified that the free plugin is fully functional on its own.<\/li>\n<\/ul>\n\n
1.1.39<\/h4>\n\n\n- Shortened older changelog entries for a cleaner WordPress.org readme.<\/li>\n<\/ul>\n\n
1.1.38<\/h4>\n\n\n- Protected automatic message read-state changes with a nonce.<\/li>\n
- Hardened reCAPTCHA response handling and duplicate form redirects.<\/li>\n<\/ul>\n\n
1.1.37<\/h4>\n\n\n- Tightened request handling for admin notices, notification settings, SMTP tests, and frontend submissions.<\/li>\n
- Sanitized local request arrays before passing them into internal helpers.<\/li>\n<\/ul>\n\n
1.1.36<\/h4>\n\n\n- Sanitized structured form editor settings before extension filters run.<\/li>\n
- Escaped custom field HTML returned by extension filters with a strict allowlist.<\/li>\n
- Passed sanitized email preview context to extension filters.<\/li>\n<\/ul>\n\n
1.1.35<\/h4>\n\n\n- Reworked message and mail log list queries to avoid dynamically interpolated SQL fragments.<\/li>\n
- Reworked setup wizard shortcode detection to avoid interpolated IN placeholders.<\/li>\n
- Tightened sanitization for submitted field values, SMTP\/reCAPTCHA settings, and onboarding redirects.<\/li>\n<\/ul>\n\n
1.1.34<\/h4>\n\n\n- Improved translation cleanup and clarified rate-limit help text.<\/li>\n<\/ul>\n\n
1.1.33<\/h4>\n\n\n- Rechecked custom SQL reads and raised the minimum WordPress version to 6.2.<\/li>\n<\/ul>\n\n
1.1.32<\/h4>\n\n\n- Refined extension hooks for external add-ons.<\/li>\n<\/ul>\n\n
1.1.31<\/h4>\n\n\n- Rechecked message, log, dashboard, and CSV database reads.<\/li>\n<\/ul>\n\n
1.1.30<\/h4>\n\n\n- Cleaned package contents and prepared SQL reads.<\/li>\n<\/ul>\n\n
1.1.29<\/h4>\n\n\n- Added a shortcode copy box below the Publish panel.<\/li>\n<\/ul>\n\n
1.1.28<\/h4>\n\n\n- Standardized the public plugin brand spelling.<\/li>\n<\/ul>\n\n
1.1.27<\/h4>\n\n\n- Fixed notification preview compatibility and Czech translations.<\/li>\n<\/ul>\n\n
1.1.26<\/h4>\n\n\n- Cleaned stale translation strings.<\/li>\n<\/ul>\n\n
1.1.25<\/h4>\n\n\n- Renamed the plugin, aligned the text domain, and documented Google reCAPTCHA.<\/li>\n<\/ul>\n\n
1.1.24<\/h4>\n\n\n- Improved Gutenberg block controls.<\/li>\n<\/ul>\n\n
1.1.23<\/h4>\n\n\n- Split editor, frontend, notification, onboarding, message, settings, and admin action code into focused traits.<\/li>\n<\/ul>\n\n
1.1.22<\/h4>\n\n\n- Split SMTP handling and CSV export into dedicated classes.<\/li>\n<\/ul>\n\n
1.1.21<\/h4>\n\n\n- Hardened frontend option validation and proxy IP handling.<\/li>\n<\/ul>\n\n
1.1.20<\/h4>\n\n\n- Refined Plugin Check annotations for mail log queries.<\/li>\n<\/ul>","raw_excerpt":"Secure contact form with a visual form builder, AJAX submissions, stored messages, email notifications, mail logs, SMTP settings, and CSV export.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/323800","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=323800"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/mailfix"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=323800"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=323800"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=323800"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=323800"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=323800"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=323800"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}