{"id":368747,"date":"2026-09-16T08:48:04","date_gmt":"2026-09-16T08:48:04","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/uno-wp-form\/"},"modified":"2026-09-16T11:07:23","modified_gmt":"2026-09-16T11:07:23","slug":"unomoon-form","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/unomoon-form\/","author":9141155,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"5.1.6.3","stable_tag":"5.1.6.3","tested":"7.1","requires":"6.0","requires_php":"8.0","requires_plugins":null,"header_name":"Unomoon Form","header_author":"annrie","header_description":"Shortcode-based contact form with a confirmation screen. A maintained fork of MW WP Form, tracking its security fixes and verified on WordPress 7.","assets_banners_color":"","last_updated":"2026-09-16 11:07:23","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/cielos.phantomoon.com\/unomoon-form\/","header_author_uri":"https:\/\/phantomoon.com","rating":0,"author_block_rating":0,"active_installs":0,"downloads":55,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"5.1.6.2":{"tag":"5.1.6.2","author":"annrie","date":"2026-09-16 08:47:46","revision":3698206},"5.1.6.3":{"tag":"5.1.6.3","author":"annrie","date":"2026-09-16 11:07:23","revision":3698414}},"upgrade_notice":{"5.1.6.2":"

The plugin was renamed to Unomoon Form and every identifier changed. If you are upgrading from Uno WP Form, back up your database and run the migration script from the GitHub repository before activating this version. Also a security hardening release.<\/p>","5.1.6.1":"

Security release. Fixes shortcode execution on the completion screen, which is reachable by unauthenticated visitors, and tightens output escaping on the inquiry data list screen. Updating is recommended.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3698414,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3698414,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3698414,"resolution":false,"location":"assets","locale":false}},"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["5.1.6.2","5.1.6.3"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3698206,"resolution":"1","location":"assets","locale":"","width":1568,"height":739},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3698206,"resolution":"2","location":"assets","locale":"","width":1568,"height":739},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3698206,"resolution":"3","location":"assets","locale":"","width":1568,"height":739},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3698206,"resolution":"4","location":"assets","locale":"","width":1568,"height":739},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3698206,"resolution":"5","location":"assets","locale":"","width":1568,"height":739}},"screenshots":{"1":"Form editing screen. The form body is written with shortcodes, and the auto-reply mail settings sit beside it.","2":"Form tag generator. Pick a field type and it builds the shortcode for you.","3":"Validation rules and admin notification mail settings.","4":"Saved inquiry data. Each form field becomes a column.","5":"Chart built from the saved inquiry data."}},"plugin_section":[],"plugin_tags":[19336,358,361,450,80],"plugin_category":[41,42,43],"plugin_contributors":[281020],"plugin_business_model":[],"class_list":["post-368747","plugin","type-plugin","status-publish","hentry","plugin_tags-confirm","plugin_tags-contact-form","plugin_tags-form","plugin_tags-mail","plugin_tags-shortcode","plugin_category-communication","plugin_category-contact-forms","plugin_category-customization","plugin_contributors-annrie","plugin_committers-annrie"],"banners":[],"icons":{"svg":"https:\/\/ps.w.org\/unomoon-form\/assets\/icon.svg?rev=3698414","icon":"https:\/\/ps.w.org\/unomoon-form\/assets\/icon.svg?rev=3698414","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/unomoon-form\/assets\/screenshot-1.png?rev=3698206","caption":"Form editing screen. The form body is written with shortcodes, and the auto-reply mail settings sit beside it."},{"src":"https:\/\/ps.w.org\/unomoon-form\/assets\/screenshot-2.png?rev=3698206","caption":"Form tag generator. Pick a field type and it builds the shortcode for you."},{"src":"https:\/\/ps.w.org\/unomoon-form\/assets\/screenshot-3.png?rev=3698206","caption":"Validation rules and admin notification mail settings."},{"src":"https:\/\/ps.w.org\/unomoon-form\/assets\/screenshot-4.png?rev=3698206","caption":"Saved inquiry data. Each form field becomes a column."},{"src":"https:\/\/ps.w.org\/unomoon-form\/assets\/screenshot-5.png?rev=3698206","caption":"Chart built from the saved inquiry data."}],"raw_content":"\n

Unomoon Form creates mail forms with confirmation screens using shortcodes. It is a GPL fork of MW WP Form by inc2734 \/ Web \u306e\u76f8\u8ac7\u6240.<\/p>\n\n

Unomoon Form \u306f\u3001\u30b7\u30e7\u30fc\u30c8\u30b3\u30fc\u30c9\u3067\u78ba\u8a8d\u753b\u9762\u4ed8\u304d\u306e\u30e1\u30fc\u30eb\u30d5\u30a9\u30fc\u30e0\u3092\u4f5c\u6210\u3067\u304d\u307e\u3059\u3002MW WP Form \u306e GPL \u30d5\u30a9\u30fc\u30af\u3067\u3059\u3002<\/p>\n\n

Why this fork exists<\/h4>\n\n

The upstream project states on its official site that development is halted except for vulnerability fixes<\/strong>, that it will not re-verify the plugin each time WordPress is updated<\/strong>, and that users should consider migrating to another plugin. As of this writing, upstream is still marked \"tested up to 6.4\" while WordPress 7.1 has shipped.<\/p>\n\n

This fork exists to do the two things upstream has stopped doing:<\/p>\n\n

    \n
  1. Track upstream security fixes.<\/strong> Every fix released upstream is ported here.<\/li>\n
  2. Keep verifying against current WordPress.<\/strong> Each release is tested on the latest WordPress.<\/li>\n<\/ol>\n\n

    Nothing about the form workflow is changed. If you are happy with MW WP Form and do not need either of the above, there is no reason to switch.<\/p>\n\n

    \u4e0a\u6d41\u306f\u516c\u5f0f\u30b5\u30a4\u30c8\u3067\u300c\u958b\u767a\u306f\u8106\u5f31\u6027\u5bfe\u5fdc\u3092\u9664\u304d\u505c\u6b62\u300d\u300cWordPress \u306e\u30a2\u30c3\u30d7\u30c7\u30fc\u30c8\u306e\u305f\u3073\u306b\u52d5\u4f5c\u78ba\u8a8d\u306f\u3057\u306a\u3044\u300d\u300c\u4ed6\u306e\u30d7\u30e9\u30b0\u30a4\u30f3\u3078\u306e\u4e57\u308a\u63db\u3048\u3092\u691c\u8a0e\u3057\u3066\u307b\u3057\u3044\u300d\u3068\u8868\u660e\u3057\u3066\u3044\u307e\u3059\u3002\u672c\u30d5\u30a9\u30fc\u30af\u306f\u3001\u4e0a\u6d41\u304c\u884c\u308f\u306a\u304f\u306a\u3063\u305f \u30bb\u30ad\u30e5\u30ea\u30c6\u30a3\u4fee\u6b63\u306e\u8ffd\u968f<\/strong> \u3068 \u6700\u65b0 WordPress \u3067\u306e\u52d5\u4f5c\u691c\u8a3c<\/strong> \u3092\u5f15\u304d\u53d7\u3051\u308b\u3053\u3068\u3092\u76ee\u7684\u3068\u3057\u3066\u3044\u307e\u3059\u3002\u30d5\u30a9\u30fc\u30e0\u306e\u4f5c\u6210\u30d5\u30ed\u30fc\u81ea\u4f53\u306f\u5909\u66f4\u3057\u3066\u3044\u307e\u305b\u3093\u3002<\/p>\n\n

    Differences from MW WP Form<\/h4>\n\n

    This fork migrates plugin identifiers, post types, shortcode prefixes, hooks, assets and admin labels to the unomoon-form<\/code> \/ unomoonform_*<\/code> namespace. Shortcodes are not compatible<\/strong>: [mwform_text]<\/code> becomes [unomoonform_text]<\/code>, and so on. The two plugins can therefore be installed side by side, but forms are not shared between them.<\/p>\n\n

    \u30d7\u30e9\u30b0\u30a4\u30f3\u8b58\u5225\u5b50\u3001\u6295\u7a3f\u30bf\u30a4\u30d7\u3001\u30b7\u30e7\u30fc\u30c8\u30b3\u30fc\u30c9\u63a5\u982d\u8f9e\u3001\u30d5\u30c3\u30af\u3001\u30a2\u30bb\u30c3\u30c8\u3001\u7ba1\u7406\u753b\u9762\u30e9\u30d9\u30eb\u3092 unomoon-form<\/code> \/ unomoonform_*<\/code> \u540d\u524d\u7a7a\u9593\u3078\u79fb\u884c\u3057\u3066\u3044\u307e\u3059\u3002\u30b7\u30e7\u30fc\u30c8\u30b3\u30fc\u30c9\u306b\u4e92\u63db\u6027\u306f\u3042\u308a\u307e\u305b\u3093\u3002<\/strong><\/p>\n\n

    Features<\/h4>\n\n
      \n
    • Shortcode-based form creation<\/li>\n
    • Confirmation screen<\/li>\n
    • Same-page or separate-page transitions<\/li>\n
    • Validation rules<\/li>\n
    • Admin notification email and automatic reply email<\/li>\n
    • Inquiry data storage<\/li>\n
    • Chart display for saved inquiry data<\/li>\n
    • Japanese translation available<\/li>\n<\/ul>\n\n

      \u4e3b\u306a\u6a5f\u80fd: \u30b7\u30e7\u30fc\u30c8\u30b3\u30fc\u30c9\u306b\u3088\u308b\u30d5\u30a9\u30fc\u30e0\u4f5c\u6210\uff0f\u78ba\u8a8d\u753b\u9762\uff0f\u540c\u4e00URL\u307e\u305f\u306f\u500b\u5225URL\u3067\u306e\u753b\u9762\u9077\u79fb\uff0f\u30d0\u30ea\u30c7\u30fc\u30b7\u30e7\u30f3\u30eb\u30fc\u30eb\uff0f\u7ba1\u7406\u8005\u5b9b\u30e1\u30fc\u30eb\u3068\u81ea\u52d5\u8fd4\u4fe1\u30e1\u30fc\u30eb\uff0f\u554f\u3044\u5408\u308f\u305b\u30c7\u30fc\u30bf\u4fdd\u5b58\uff0f\u4fdd\u5b58\u30c7\u30fc\u30bf\u306e\u30b0\u30e9\u30d5\u8868\u793a\uff0f\u65e5\u672c\u8a9e\u5bfe\u5fdc<\/p>\n\n

      Documentation<\/h4>\n\n

      Japanese documentation, including how this fork differs from MW WP Form and the things people commonly trip over: https:\/\/cielos.phantomoon.com\/unomoon-form\/<\/p>\n\n

      Credits<\/h4>\n\n

      Original plugin: MW WP Form by inc2734, currently maintained by Web \u306e\u76f8\u8ac7\u6240.\nUpstream repository: https:\/\/github.com\/web-soudan\/mw-wp-form\nUpstream site: https:\/\/mw-wp-form.web-soudan.co.jp<\/p>\n\n

      Third-party resources<\/h4>\n\n

      The following libraries are bundled with the plugin. No external scripts, styles or fonts are loaded at runtime.<\/p>\n\n

        \n
      • Chart.js (MIT) \u2014 renders the inquiry data charts. https:\/\/www.chartjs.org\/ \/ https:\/\/github.com\/chartjs\/Chart.js<\/li>\n
      • jQuery UI \"smoothness\" theme CSS (MIT) \u2014 styles the date picker and admin widgets. https:\/\/jqueryui.com\/ \/ https:\/\/github.com\/jquery\/jquery-ui<\/li>\n
      • jQuery UI MonthPicker (MIT) \u2014 month picker widget. https:\/\/github.com\/KidSysco\/jquery-ui-month-picker<\/li>\n<\/ul>\n\n\n
          \n
        1. Upload the unomoon-form<\/code> folder to the \/wp-content\/plugins\/<\/code> directory.<\/li>\n
        2. Activate the plugin through the Plugins<\/code> menu in WordPress.<\/li>\n
        3. Create a form from the Unomoon Form admin screen.<\/li>\n

        4. Place the generated shortcode on a page.<\/p><\/li>\n

        5. unomoon-form<\/code> \u30d5\u30a9\u30eb\u30c0\u3092 \/wp-content\/plugins\/<\/code> \u3078\u30a2\u30c3\u30d7\u30ed\u30fc\u30c9\u3057\u307e\u3059\u3002<\/p><\/li>\n

        6. \u7ba1\u7406\u753b\u9762\u306e\u300c\u30d7\u30e9\u30b0\u30a4\u30f3\u300d\u304b\u3089\u6709\u52b9\u5316\u3057\u307e\u3059\u3002<\/li>\n
        7. Unomoon Form \u306e\u7ba1\u7406\u753b\u9762\u3067\u30d5\u30a9\u30fc\u30e0\u3092\u4f5c\u6210\u3057\u307e\u3059\u3002<\/li>\n
        8. \u751f\u6210\u3055\u308c\u305f\u30b7\u30e7\u30fc\u30c8\u30b3\u30fc\u30c9\u3092\u56fa\u5b9a\u30da\u30fc\u30b8\u306a\u3069\u306b\u914d\u7f6e\u3057\u307e\u3059\u3002<\/li>\n<\/ol>\n\n\n
          \n

          Can I use MW WP Form shortcodes as-is?<\/h3><\/dt>\n

          No. This fork uses the unomoonform_*<\/code> shortcode namespace. [mwform_text]<\/code> becomes [unomoonform_text]<\/code>, [mwform_submitButton]<\/code> becomes [unomoonform_submitButton]<\/code>, and so on. Hooks follow the same rule (mwform_*<\/code> becomes unomoonform_*<\/code>).<\/p>\n\n

          \u3044\u3044\u3048\u3002unomoonform_*<\/code> \u540d\u524d\u7a7a\u9593\u3092\u4f7f\u7528\u3057\u307e\u3059\u3002\u30d5\u30c3\u30af\u3082\u540c\u69d8\u3067\u3059\u3002<\/p><\/dd>\n

          Can I run this alongside MW WP Form?<\/h3><\/dt>\n

          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.<\/p>\n\n

          \u306f\u3044\u3002\u8b58\u5225\u5b50\u30fb\u6295\u7a3f\u30bf\u30a4\u30d7\u30fbDB\u30ad\u30fc\u304c\u3059\u3079\u3066\u5225\u306a\u306e\u3067\u885d\u7a81\u3057\u307e\u305b\u3093\u3002\u305f\u3060\u3057\u30d5\u30a9\u30fc\u30e0\u306f\u5171\u6709\u3055\u308c\u306a\u3044\u305f\u3081\u3001\u4f5c\u308a\u76f4\u3057\u304c\u5fc5\u8981\u3067\u3059\u3002<\/p><\/dd>\n

          What are the submit button attributes?<\/h3><\/dt>\n

          [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<\/code>, and on the confirmation screen it renders the send button labelled with submit_value<\/code>.<\/p>\n\n

          Note that unrecognised attributes are silently ignored, and the Japanese defaults happen to read \"\u78ba\u8a8d\u753b\u9762\u3078\" and \"\u9001\u4fe1\u3059\u308b\" \u2014 so a misspelled attribute can still look correct. To place the buttons separately, use [unomoonform_confirmButton]<\/code> and [unomoonform_submitButton]<\/code>.<\/p>\n\n

          \u9001\u4fe1\u30dc\u30bf\u30f3\u306f [unomoonform_submitButton confirm_value=\"...\" submit_value=\"...\"]<\/code> \u3067\u3059\u30021\u3064\u306e\u30bf\u30b0\u304c\u5165\u529b\u753b\u9762\u3068\u78ba\u8a8d\u753b\u9762\u306e\u4e21\u65b9\u3092\u517c\u306d\u307e\u3059\u3002\u6307\u5b9a\u3055\u308c\u3066\u3044\u306a\u3044\u5c5e\u6027\u306f\u9ed9\u3063\u3066\u7121\u8996\u3055\u308c\u308b<\/strong>\u305f\u3081\u3001\u5c5e\u6027\u540d\u3092\u9593\u9055\u3048\u3066\u3082\u65e2\u5b9a\u306e\u30e9\u30d9\u30eb\u3067\u6b63\u3057\u304f\u52d5\u3044\u3066\u3044\u308b\u3088\u3046\u306b\u898b\u3048\u308b\u3053\u3068\u304c\u3042\u308a\u307e\u3059\u3002<\/p><\/dd>\n

          Where should I report issues?<\/h3><\/dt>\n

          Please use GitHub Issues: https:\/\/github.com\/annrie\/unomoon-form\/issues<\/p><\/dd>\n\n<\/dl>\n\n\n

          Version numbers are <upstream version>.<fork release><\/code>. 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<\/code> suffix (5.1.6-uno.1). The suffix was dropped because stable tags here may contain only numbers and periods.<\/p>\n\n

          5.1.6.3<\/h4>\n\n
            \n
          • Resolved all Plugin Check warnings. Intentional error_log()<\/code> calls (mail delivery and upload failures) and the transient-cached direct query are now annotated with the reason; template variables set by _render()<\/code> are marked as method-local.<\/li>\n
          • Replaced the no-op error handler around the session cookie with a headers_sent()<\/code> guard, matching the CSRF cookie code.<\/li>\n
          • Added a plugin icon for the WordPress.org directory.<\/li>\n<\/ul>\n\n

            5.1.6.2<\/h4>\n\n
              \n
            • Renamed the plugin from \"Uno WP Form\" to \"Unomoon Form\" to comply with the WordPress.org naming rules. All identifiers moved to the unomoon-form<\/code> \/ unomoonform_*<\/code> namespace: shortcodes are now [unomoonform_*]<\/code>, hooks unomoonform_*<\/code>, the form post type unomoon-form<\/code>. Sites migrating from Uno WP Form must run the migration script shipped in the GitHub repository (tools\/migrate-from-uno-wp-form.php<\/code>).<\/li>\n
            • Replaced Google Charts with a bundled copy of Chart.js, and bundled the jQuery UI theme CSS. The plugin no longer loads anything from external servers.<\/li>\n
            • Security: Bound session data to a plugin-prefixed transient key and validate the session cookie format.<\/li>\n
            • Security: Sanitize all request input (nonce values, settings, inquiry data, chart settings, query strings, server variables) and escape placeholder values substituted into form content.<\/li>\n
            • Security: Use wp_handle_upload()<\/code> for temporary file uploads and generate attachment metadata for saved files.<\/li>\n
            • Removed the mail debug log written to the uploads directory.<\/li>\n
            • Moved inline scripts and styles to wp_add_inline_script()<\/code> \/ wp_add_inline_style()<\/code>.<\/li>\n
            • Added direct-access guards to every PHP file.<\/li>\n
            • Translations are now delivered through translate.wordpress.org instead of bundled files.<\/li>\n<\/ul>\n\n

              5.1.6.1<\/h4>\n\n
                \n
              • Changed the version numbering scheme, dropping the -uno.N<\/code> suffix. Same code as 5.1.6-uno.1 on GitHub.<\/li>\n
              • Security: Neutralize shortcode syntax in values rendered on the completion screen. A shortcode typed into a form field was executed when the completion screen substituted the value. Ported from upstream 5.1.5.<\/li>\n
              • Security: Tighten output escaping on the inquiry data list screen. Meta keys derive from mail-content tags and were printed verbatim into HTML id \/ class attributes and the Screen Options panel. Column identifiers are now mapped to safe slugs. Ported from upstream 5.1.5 and 5.1.6.<\/li>\n
              • Security: Add output escaping to the dynamic column labels, response_status<\/code> and admin_mail_to<\/code>. Ported from upstream 5.1.5.<\/li>\n
              • Tested on WordPress 7.1.<\/li>\n<\/ul>\n\n

                5.1.4.1<\/h4>\n\n
                  \n
                • Initial release of the fork, based on MW WP Form 5.1.4.<\/li>\n
                • Migrated identifiers, post types, shortcode prefixes, hooks, assets and admin labels to the uno-wp-form<\/code> \/ unoform_*<\/code> namespace (renamed again to unomoon-form<\/code> \/ unomoonform_*<\/code> in 5.1.6.2).<\/li>\n<\/ul>","raw_excerpt":"Shortcode-based contact form with a confirmation screen. A maintained fork of MW WP Form, tracking its security fixes and verified on WordPress 7.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/368747","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=368747"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/annrie"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=368747"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=368747"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=368747"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=368747"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=368747"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=368747"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}