Validation Muse for Contact Form 7
| 开发者 | simmotorlp |
|---|---|
| 更新时间 | 2026年7月3日 21:11 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
Validation Muse lets you write your own validation rules and error messages for every Contact Form 7 field — directly in the form editor, per form, per field. No code, no global settings page, no JavaScript hacks.
Most CF7 validation plugins broke when Contact Form 7 6.x introduced Schema-based Validation (SWV). Validation Muse runs its filters at priority 20 (after CF7 core) and uses Reflection to replace SWV error text on already-invalidated fields, so your custom copy actually shows up — even on the new validation engine.
Why Validation Muse
- CF7 6.x SWV compatible — works with the new Schema-based Validation engine, not just legacy hooks.
- Custom Regex & Length Rules — define custom regular expression patterns, min length, and max length rules per field with their own error messages.
- Conditional "Required-If" Rules — make fields required only when a companion field is filled/checked.
- Client-Side SWV Integration — standard validation rules (required, email, length) are injected into CF7's native SWV engine for instant frontend feedback with full accessibility (A11y) support.
- Rule Sets Import/Export & Templates — export/import validation rules as JSON, copy them from other forms, and bulk apply global templates.
- Placeholder Tokens — use
{field_label},{min}, and{max}in validation messages to generate dynamic texts. - Per-form, per-field — each form keeps its own messages; no global override.
- Stored in post meta — messages live with the form, compatible with CF7 form duplication and third-party CF7 import/export plugins.
- Multilingual via WPML, Polylang & Flavor — translates rules using standard WPML/Polylang hooks, and features language tabs + one-click AI Translate when Flavor is active.
- Developer-friendly — extensibility hooks
vmcf7_loadedandvmcf7_validation_tag_typeslet you add custom field types. - Lightweight — no admin bloat, no tracking, no upsells.
- Required-field messages: any required tag (
text,textarea,select,checkbox,radio,file, etc.). - Invalid-format messages:
email,url,tel,number(includingrange),date, andtimefields. - Custom error messages on validation failure:
file(size/type checks),acceptance(unchecked/unaccepted state), andquiz(incorrect answer). - HTML inside messages is allowed and sanitized through
wp_kses_post(). - Custom Regex and Min/Max Length rules support all input fields (excluding acceptance and quiz).
.pot file and is already translated into German, Spanish, French, Portuguese (Brazil), Russian, and Ukrainian. Help translate it into your language.
安装:
- Install from Plugins → Add New and search for Validation Muse for Contact Form 7, or upload the
validation-muse-for-contact-form-7folder to/wp-content/plugins/. - Activate the plugin. Contact Form 7 must already be active — Validation Muse will deactivate itself with an admin notice if it is not.
- Edit any Contact Form 7 form, open the Custom Validation panel, enable it, and write your messages.
- (Optional) Install the Flavor translation plugin to translate messages per language with AI assistance.
屏幕截图:
常见问题:
Does this work with Contact Form 7 6.x and Schema-based Validation (SWV)?
Yes. Since version 1.3.0, Validation Muse hooks at priority 20 (after CF7 core) and uses Reflection to replace SWV error text on already-invalidated fields. Since 1.6.1, standard rules (required, email/url/tel/number/date/time, min/max length) are also injected directly into CF7's own SWV schema, so client-side (frontend JS) validation shows your custom messages instantly — through CF7's native validation engine, with no extra script from this plugin.
How is this different from other CF7 validation plugins?
Validation Muse is the only CF7 validation plugin that (1) is compatible with CF7 6.x SWV out of the box — both server-side and in CF7's own client-side validation, (2) stores messages in form post meta so they live with the form (compatible with CF7 form duplication and import/export plugins), and (3) integrates with the Flavor translation plugin for per-language messages with one-click AI translation.
Can I translate validation messages per language?
Yes — install the Flavor translation plugin and Validation Muse will show language tabs in the form editor plus an AI Translate button. Translations are stored in Flavor's database; uninstalling Validation Muse cleans them up.
Which field types support custom invalid or validation failure messages?
email,url,tel,number(includingrange),date, andtimesupport custom invalid-format messages.filesupports custom file size/type validation error messages.acceptancesupports custom error messages when the checkbox is not accepted.quizsupports custom error messages when the answer is incorrect.- Any required field of any type can have a custom required-field message.
Where are the messages stored?
In each form's post meta. They live with the form, so duplicating a form (built into CF7) keeps the messages. CF7 has no native export, but third-party CF7 import/export plugins read post meta — so migrations across sites work without a separate import step.
Can I use HTML in validation messages?
Yes, basic HTML is allowed and sanitized via wp_kses_post().
Does this plugin require Contact Form 7?
Yes. CF7 must be installed and active. The plugin shows an admin notice and self-deactivates if CF7 is missing.
Is there a settings page?
No. Configuration lives inside each form, in the Custom Validation panel. There is no global settings page by design — every form keeps its own messages.
Does the plugin track or send any data?
No. Validation Muse makes no external requests. The optional AI Translate button (Flavor integration) routes through Flavor's own configured provider.
更新日志:
1.6.3
- i18n: fully regenerated the
.pottranslation template — the catalog was frozen since 1.2.0 and covered only about 20% of the plugin's translatable strings (regex/length rules, rule templates, AI Translate errors, and more were never extractable before). All six shipped languages (German, Spanish, French, Portuguese, Russian, Ukrainian) are now fully translated against the current UI. - Docs: synced all translated readme files — feature list, supported field types, and FAQ now reflect 1.6.0–1.6.2 functionality (custom regex/length rules, required-if, native SWV client-side validation, rule templates); their Changelog/Upgrade Notice sections, previously stuck at 1.4.2, now cover every release up to 1.6.2.
- Fix: added a missing
translators:comment for a placeholder string (i18n code quality, no behavior change).
- Fix: messages saved by versions prior to the plugin rename (stored under the legacy
_cf7cv_meta prefix) were invisible to the current code. A one-time migration now renames them to the_vmcf7_prefix automatically, restoring lost messages. Collision-safe and runs once.
- Fix: duplicate/overwritten validation messages on frontend by integrating with CF7's native SWV engine.
- Fix: admin panel drawers and preview cards rendered expanded due to CF7 editor panel stripping inline styles.
- New: custom regex and min/max-length validation rules per field, each with its own message.
- New: validation messages for
file,acceptance, andquizfields; conditional "required-if" messages. - New: message placeholder tokens
{field_label},{min},{max}. - New: client-side inline validation mirroring the server messages, with
aria-describedbyaccessibility. - New: live message preview, copy messages between forms, JSON import/export of message sets, and editor lint.
- New: WPML/Polylang string registration alongside the Flavor bridge; translation import/export.
- Minimum PHP raised to 8.0; minimum WordPress raised to 6.0; tested up to WordPress 7.0.
- New: custom validation messages for
timefields. - Clearer AI Translate error feedback in the form editor.
- Reflection-based SWV message replacement now logs failures under WP_DEBUG for easier diagnosis.
- Improved handling of pending translations (no more silent fallback) with per-request caching.
- Code modernized to PHP 8 idioms; output escaping hardened; first unit-test suite added.
- Plugin URI: now points to the dedicated landing page at https://plugins.symonov.com/validation-muse-for-cf7/
- No code or behavior changes
- Readme: USP-first rewrite for SEO discoverability
- Tags: replaced generic
messages/forms/customizationwith targetedcontact-form-7,cf7,validation,error-message,multilingual - FAQ: added entries for CF7 6.x SWV compatibility, comparison with other CF7 validation plugins, and multilingual via Flavor
- Added multilingual support via Flavor translation plugin integration
- Validation messages can now be translated per language in the form editor
- Language tabs appear automatically when Flavor plugin is active
- AI Translate button for one-click machine translation of all messages
- Translations stored in Flavor's database, keeping plugin data portable
- Zero overhead when Flavor is not installed — all calls behind class_exists() checks
- Flavor translations cleaned up on plugin uninstall
- Fixed compatibility with Contact Form 7 6.x SWV (Schema-based Validation)
- Validation filters now run at priority 20 (after CF7 core) to replace SWV error messages
- Added Reflection-based error replacement for already-invalidated fields
- Custom messages now correctly override default CF7 "The field is required." text
- Fixed variable name mismatch causing "No required fields" error
- Refactored codebase to follow WordPress Coding Standards
- Reorganized file structure for better maintainability
- Added PHPDoc blocks to all functions and methods
- Improved accessibility with ARIA labels
- Fixed JavaScript prefix inconsistency
- Fixed uninstall script to use correct meta prefix
- Added extensibility hooks (
vmcf7_loaded,vmcf7_validation_tag_types) - Changed capability check from
manage_optionstowpcf7_edit_contact_forms - Updated POT file name to match text domain
- Changed plugin name.
- Added .gitignore file.
- Added WordPress repository collateral (readme, license, POT file).
- Reworked validation hooks to override required and invalid messages without relying on AJAX filters.
- Hardened sanitization, text domain loading, and uninstall cleanup for release readiness.
- Initial public iteration bundled with the project.