From 5c3be69c7878175e4cb4f6d6d48436fb60766094 Mon Sep 17 00:00:00 2001
From: Alex P <alex.pantec@gmail.com>
Date: Tue, 12 Sep 2023 10:02:15 +0300
Subject: [PATCH] Fix complex form data during form saving

Similarly to #1510, sending encoded form and using parse_str for FormSaver, which was still using the old way.
---
 modules/ppcp-button/resources/js/modules/Helper/FormSaver.js | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/modules/ppcp-button/resources/js/modules/Helper/FormSaver.js b/modules/ppcp-button/resources/js/modules/Helper/FormSaver.js
index 494aa354f..0250b6b29 100644
--- a/modules/ppcp-button/resources/js/modules/Helper/FormSaver.js
+++ b/modules/ppcp-button/resources/js/modules/Helper/FormSaver.js
@@ -6,7 +6,6 @@ export default class FormSaver {
 
     async save(form) {
         const formData = new FormData(form);
-        const formJsonObj = Object.fromEntries(formData.entries());
 
         const res = await fetch(this.url, {
             method: 'POST',
@@ -16,7 +15,7 @@ export default class FormSaver {
             credentials: 'same-origin',
             body: JSON.stringify({
                 nonce: this.nonce,
-                form: formJsonObj,
+                form_encoded: new URLSearchParams(formData).toString(),
             }),
         });