| 开发者 | annrie |
|---|---|
| 更新时间 | 2026年9月16日 19:07 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
unomoon-form / unomoonform_* namespace. Shortcodes are not compatible: [mwform_text] becomes [unomoonform_text], and so on. The two plugins can therefore be installed side by side, but forms are not shared between them.
プラグイン識別子、投稿タイプ、ショートコード接頭辞、フック、アセット、管理画面ラベルを unomoon-form / unomoonform_* 名前空間へ移行しています。ショートコードに互換性はありません。
Features
unomoon-form folder to the /wp-content/plugins/ directory.Plugins menu in WordPress.unomoon-form フォルダを /wp-content/plugins/ へアップロードします。No. This fork uses the unomoonform_* shortcode namespace. [mwform_text] becomes [unomoonform_text], [mwform_submitButton] becomes [unomoonform_submitButton], and so on. Hooks follow the same rule (mwform_* becomes unomoonform_*).
いいえ。unomoonform_* 名前空間を使用します。フックも同様です。
Yes. Identifiers, post types and database keys are all distinct, so the two plugins do not collide. Forms are not shared between them, so each form must be recreated. はい。識別子・投稿タイプ・ DB キーがすべて別なので衝突しません。ただしフォームは共有されないため、作り直しが必要です。
[unomoonform_submitButton confirm_value="..." submit_value="..."]. One tag covers both screens: on the input screen it renders the "go to confirmation" button labelled with confirm_value, and on the confirmation screen it renders the send button labelled with submit_value.
Note that unrecognised attributes are silently ignored, and the Japanese defaults happen to read "確認画面へ" and "送信する" — so a misspelled attribute can still look correct. To place the buttons separately, use [unomoonform_confirmButton] and [unomoonform_submitButton].
送信ボタンは [unomoonform_submitButton confirm_value="..." submit_value="..."] です。1 つのタグが入力画面と確認画面の両方を兼ねます。指定されていない属性は黙って無視されるため、属性名を間違えても既定のラベルで正しく動いているように見えることがあります。
Please use GitHub Issues: https://github.com/annrie/unomoon-form/issues
<upstream version>.<fork release>. For example 5.1.6.1 is the first fork release that has caught up with upstream 5.1.6; a fix of our own on top of it would be 5.1.6.2, and catching up with upstream 5.1.7 would be 5.1.7.1. Releases before this plugin was submitted to the directory were published on GitHub only, and used a -uno.N suffix (5.1.6-uno.1). The suffix was dropped because stable tags here may contain only numbers and periods.
5.1.6.3
error_log() calls (mail delivery and upload failures) and the transient-cached direct query are now annotated with the reason; template variables set by _render() are marked as method-local.headers_sent() guard, matching the CSRF cookie code.unomoon-form / unomoonform_* namespace: shortcodes are now [unomoonform_*], hooks unomoonform_*, the form post type unomoon-form. Sites migrating from Uno WP Form must run the migration script shipped in the GitHub repository (tools/migrate-from-uno-wp-form.php).wp_handle_upload() for temporary file uploads and generate attachment metadata for saved files.wp_add_inline_script() / wp_add_inline_style().-uno.N suffix. Same code as 5.1.6-uno.1 on GitHub.response_status and admin_mail_to. Ported from upstream 5.1.5.uno-wp-form / unoform_* namespace (renamed again to unomoon-form / unomoonform_* in 5.1.6.2).