Kaze Contact Form
Kaze Contact Form
Description
Kaze Contact Form is a contact form plugin for WordPress sites that need a Japanese-friendly administration experience.
It provides a three-step input, confirmation, and completion flow, entry storage, mail notifications, CSV export,
WordPress Privacy Tools integration, and tools for moving form definitions from MW WP Form.
The plugin focuses on the core workflows needed to operate contact forms after migration. It is not a complete
drop-in replacement for every MW WP Form extension point, but it keeps the main visible behaviors traceable and
documents the intentional differences.
Features
- Multiple form management with the
[kaze_contact_form id="123"]shortcode. - Input, confirmation, and completion screens.
- Optional smooth scrolling to the form after confirmation, back, validation-error, and completion transitions.
- Field types including
text,email,tel,textarea,select,radio,checkbox, and date fields. - Server-side validation for required fields, email addresses, telephone numbers, postal codes, and length limits.
- Browser and server validation requiring at least one selection in required checkbox groups.
- Administrator mail, auto-reply mail, sender settings, and Return-Path support.
- Entry storage, entry detail screens, and CSV export.
- JSON export and import for form definitions.
- Honeypot and rate limit checks.
- Optional Akismet spam checks when the Akismet plugin and API key are configured.
- Per-form Google reCAPTCHA v3 enablement with a fixed 0.5 score threshold.
- WordPress Privacy Tools exporter and eraser integration.
- Administration tools for MW WP Form migration.
- Japanese administration UI and the
kaze-contact-formtext domain.
Installation
From the WordPress.org plugin directory
- In the WordPress administration screen, go to Plugins > Add New.
- Search for “Kaze Contact Form”.
- Click Install Now, then activate Kaze Contact Form.
From a ZIP file
- Prepare the Kaze Contact Form ZIP file.
- In the WordPress administration screen, go to Plugins > Add New > Upload Plugin.
- Select the ZIP file, click Install Now, then activate Kaze Contact Form.
Faq
No. Data is preserved by default. It is deleted only when the explicit uninstall data deletion option is enabled.
On multisite installations, uninstall cleanup runs for the site where the plugin data deletion option is enabled. It does not guarantee network-wide deletion for every site.
When entry storage is enabled, submitted form values are stored as entries. Depending on the form storage settings, entries can also store the submitter IP address and user agent. Stored entries are available through the WordPress Privacy Tools exporter and eraser integration.
Uploaded files are stored in a protected temporary directory before the submission is completed. If entry storage is enabled, completed uploads are moved to a plugin-specific subdirectory inside the WordPress uploads directory and registered as Media Library attachments, so the attachment URL can be publicly reachable depending on the site’s media access configuration. If entry storage is disabled, uploaded files are used for mail attachments during submission processing and then removed from temporary storage.
Yes, but only when the Akismet plugin is active, an API key is configured, and Kaze Contact Form has Akismet field mappings for the form. In that case, the plugin sends data to the Akismet service for spam checking.
The submitted data can include the site URL, language and character set, submitter IP address, user agent, referrer, form page URL, submitted values mapped to the Akismet author, email, and URL fields, a content value built from submitted form data, and selected request metadata. Some server values, such as cookies and authentication-related data, are excluded.
Akismet is an external service provided by Automattic. See Akismet, Akismet Terms of Use, and Akismet Privacy Policy for details.
- Akismet: https://akismet.com/
- Terms of Use: https://akismet.com/tos/
- Privacy Policy: https://akismet.com/privacy/
Create a score-based (v3) site key in Google Cloud. Enter its site key and legacy secret key on the Kaze Contact Form reCAPTCHA Settings screen, then enable reCAPTCHA v3 in each form’s Spam Protection settings. The score threshold is currently fixed at 0.5 and stored with the form settings.
Submissions are rejected when credentials are missing, the Google API cannot be reached, the response is invalid, the action does not match, or the score is below the threshold. A submission is also rejected before contacting Google when the per-form reCAPTCHA settings are invalid, duplicated, or cannot be read safely from the database. A single invalid settings row can be repaired by saving the form settings again. Duplicate rows require repair by a database administrator. Settings from MW WP Form or MW WP Form reCAPTCHA add-ons are not imported automatically.
Yes. Enabled forms load Google’s reCAPTCHA JavaScript. On submission, the plugin sends the token issued by Google to Google’s verification API. reCAPTCHA can set cookies for risk analysis. Review the site’s privacy policy and cookie notice before enabling reCAPTCHA on a form.
- reCAPTCHA: https://www.google.com/recaptcha/about/
- Google Privacy Policy: https://policies.google.com/privacy
- Google Terms of Service: https://policies.google.com/terms
No. The plugin focuses on the main user-visible workflows and migration paths, but it does not aim to reproduce every MW WP Form extension point.
Yes. The conversion processes saved inquiries in batches and does not impose a 100-inquiry total limit. Keep the legacy environment and a backup until the converted form and inquiry count have been verified.
No. Exported JSON contains only the form definition, including fields, body content, display settings, entry storage settings, spam settings, and mail settings. The reCAPTCHA enabled state and fixed 0.5 score threshold are included, but the site key and secret key are not. Submitted entries and uploaded files are managed separately through entry screens and CSV export.
Enable screen-transition scrolling in the form URL settings. The browser smoothly scrolls to the form after each transition. The kaze_contact_form_scroll_offset_{form ID} filter changes the destination in pixels. For example, return -80 from kaze_contact_form_scroll_offset_123 to leave room for a fixed header on form ID 123. The legacy MW WP Form filter name is not executed.
Reviews
Changelog
1.1.2
- Changed normal input, confirmation, back and completion transitions to one direct POST, preserving page templates, uploads, validation and duplicate-submission protection. Configured validation-error redirects remain supported.
- Added click and keyboard copying for form shortcodes and refined the form editor layout.
- Tested compatibility with WordPress 7.1.
- Minor fixes.
1.1.0
- Added a reCAPTCHA settings form.
- Changed MW WP Form migration to a one-way conversion that does not retain links between source and target forms.
- Simplified generated HTML by removing plugin-added field labels, wrappers, headings, and fallback output outside the configured form body.
- Changed form settings to preserve root-relative URLs when saved instead of converting them to absolute site URLs.
- Added optional smooth scrolling to the form after validation errors, confirmation, back navigation, and completion transitions.
- Changed post-submission screen transitions to use server-side redirects instead of an intermediate frontend redirect view.
- Changed confirmation and completion screens to return to a cleared input screen when reloaded or fetched again through browser history.
1.0.0
- Added form creation, three-step submission, entry storage, mail notifications, CSV export, form definition JSON export and import, Privacy Tools integration, and MW WP Form migration tools.