Сүрөттөө

Validation Muse lets you write your own 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.
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 Flavor — when the Flavor translation plugin is active, language tabs and a one-click AI Translate button appear in the editor automatically. Zero overhead when Flavor is not installed.
Developer-friendly — extensibility hooks vmcf7_loaded and vmcf7_validation_tag_types let you add custom field types.
Lightweight — no admin bloat, no tracking, no upsells.

Supported field types

Required-field messages: any required tag (text, textarea, select, checkbox, radio, file, etc.)
Invalid-format messages: email, url, tel, number (including range), and date.
HTML inside messages is allowed and sanitized through wp_kses_post().

Translations

The plugin ships with a .pot file and is already translated into Dutch, German, Russian, Spanish (Chile/Spain). Help translate it into your language.

Скриншоттор

The Custom Validation panel inside the Contact Form 7 editor — enable per form, write messages per field.
Per-language tabs and the AI Translate button (visible when the Flavor translation plugin is active).
Required-field message rendered on the frontend.
Invalid-format message for an email field rendered on the frontend.

Орнотуу

Install from Plugins Add New and search for Validation Muse for Contact Form 7, or upload the validation-muse-for-contact-form-7 folder 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.

FAQ.KG

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. Your custom messages override both the legacy and SWV defaults.
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, (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 messages?: email, url, tel, number (including range), and date. 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.

Сын-пикирлер

There are no reviews for this plugin.

Contributors & Developers

“Validation Muse for Contact Form 7” is open source software. The following people have contributed to this plugin.

SYMONOV

“Validation Muse for Contact Form 7” has been translated into 5 locales. Thank you to the translators for their contributions.

Translate “Validation Muse for Contact Form 7” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Өзгөртүүлөр

1.4.2

Plugin URI: now points to the dedicated landing page at https://plugins.symonov.com/validation-muse-for-cf7/
No code or behavior changes

1.4.1

Readme: USP-first rewrite for SEO discoverability
Tags: replaced generic messages/forms/customization with targeted contact-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
Tested up to WordPress 6.9.4

1.4.0

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

1.3.0

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

1.2.1

Fixed variable name mismatch causing “No required fields” error

1.2.0

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_options to wpcf7_edit_contact_forms
Updated POT file name to match text domain

1.1.2

Changed plugin name.

1.1.1

Added .gitignore file.

1.1.0

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.

1.0.1

Initial public iteration bundled with the project.

Сүрөттөө

Why Validation Muse

Supported field types

Translations

Скриншоттор

Орнотуу

FAQ.KG

Does this work with Contact Form 7 6.x and Schema-based Validation (SWV)?

How is this different from other CF7 validation plugins?

Can I translate validation messages per language?

Which field types support custom invalid messages?

Where are the messages stored?

Can I use HTML in validation messages?

Does this plugin require Contact Form 7?

Is there a settings page?

Does the plugin track or send any data?