Hello!
Have you watched this video? (https://www.loom.com/share/153ea249063e4f10a70fefd75162b921?sid=11870ccb-99dd-491f-9016-e0055b3f6fd9) at 01:50…
Please note the verification method in the developer console (window.checkoutView.model.attributes).
I also use a layout for the cart page. On the cart page, the “window.checkoutView.model.attributes” object is filled and works correctly. This only does not work for the checkout page when using a layout.
The plugin developer has investigated the issue again and has given a new comment:
I read this topic, there is no solution in it. Well, it does not help me. The problem is clearly somewhere in this checkout form.
I just went to your site again, decided to check what data is being reset. So, I filled in all the fields, selected the order pickup point, left the checkout and went back to it again and as a result, all the data, both the first and last name, the phone number and email, everything was reset. My plugin does not affect such fields as “First Name”, “Last Name”, “Phone” and “Email” at all. It only uses the values from these fields when sending data to the CDEK delivery service. And when placing an order, it does not even know about their existence. In addition, you yourself write that everything works when using the standard checkout form.
Also, I do not think that this is a matter of some hooks. I don’t know how this checkout works, of course, but I guess that the hooks that you can connect to this checkout are only template hooks, and not those that are used for the internal logic of data processing. Simply because connecting hooks that process data to a template (and your checkout is a template) makes no sense.
To make it clearer, I’ll give an example. The hook woocommerce_checkout_before_customer_details is only a template hook, because it is called directly at the time of rendering the checkout form. You can connect any additional HTML blocks to this hook that you want to be displayed at the very top of the checkout form. These hooks also include woocommerce_checkout_billing, woocommerce_checkout_shipping, woocommerce_checkout_after_customer_details, etc.
And there are hooks that affect the logic of data processing. For example, the hook woocommerce_checkout_update_order_review is triggered every time the checkout form is reloaded/updated. This hook can be used, for example, to redefine some data when the order form is reloaded/updated. But you can’t just insert some HTML block into it, since this will break the logic of Woocommerce.
One could suggest that some hook is missing and this checkout cannot save data because of this, but this is not so. And the video I sent you shows that when changing the value in the form, the data in the “checkoutView” object changes. Then, if you go from checkout to the cart, you can see that all this data is also saved in this object. But as soon as we go to checkout, all the data is empty, including the data that is not connected with the CDEK plugin.
Please check again and provide feedback!
.
