Check shipping information "telephone" is required. Enter and try again.

[Aquive]

When following the regular flow of the checkout I get an error about phonenumber missing, which actually isn't the case. When I refill the phone number after selecting a shipment method it works without an error. See error below.

Versions:

• "hyva-themes/magento2-hyva-checkout": "1.3.6",
• "tig/postnl-magento2": "1.20.1",
• "postnl/module-hyva-checkout": "1.2.0",

I haven't found a solution yet. I will add one when I have it.

[JorisPostNL]

Hi @Aquive , there is a secondary config within Magento2 itself in the customer configuration section which sets phone numbers as optional or required. When we turn this off in our test environment we do not have any issues placing orders without phone numbers. Could you check if this works for you too?

[Aquive]

Hi @JorisPostNL,

I understand that this bypasses the problem. The thing is; the phone number is required as a business requirement. So the suggestion is not an actual solution.

When the phone number is required, the checkout/fill-in flow is simply bugged.

I am discussing with the client to make the phone field optional. But the bug still remains.

Do you have any updates on progress on the overall flow? Is it somehow possible to get in touch? I am also willing to contribute where possible.

[JorisPostNL]

Hi @Aquive thanks for elaborating on the issue. I will note to include this in our tests for the overall flow changes. We are currently deploying said changes in our test environments and hope to be able to release a fix soon. If this particular issue persists despite the changes to the overall flow I will make sure to pick this up in a separate fix.

Thank you for your kind offer to assist us. We work with a dedicated IT supplier who handles all required features and fixes, but if you’d like to stay in touch, this GitHub repository is the best place. We greatly appreciate contributions from external developers and regularly review and implement pull requests submitted here. If you find a fix before we do and share it via a pull request, we’ll gladly consider it!

Kind regards
Joris - PostNL

[Aquive]

@JorisPostNL good to hear that. Any branch or tag I can test too? I'd be happy to give feedback early in the testing stages.

[JorisPostNL]

Thank you @Aquive , if we require assistance or a fresh pair of eyes with the tests I'll be sure to provide the necessary details!

Kind regards
Joris - PostNL

[Aquive]

Any updates on progress?

[JorisPostNL]

Hi @Aquive , certainly! Our supplier recently deployed an update to our testing environment and I've already put it through a round of testing. Although I did note several issues regarding the population of the delivery options menu with options depending on the config I can confirm the wrong phone number error is now gone in this latest iteration of our checkout. Our supplier is now repairing the aforementioned issues I found and we hope to be able to do a release soon.

Kind regards
Joris - PostNL

[speedupmate]

@JorisPostNL hey, we are getting more requests on this. Have you released this or does it make more sense for customers to monitor your github issues on progress ?

[JorisPostNL]

Hi @speedupmate , we are currently still finetuning the check-out form validation so it has not been released yet. We hope to be able to release the update soon.

Kind regards
Joris - PostNL

[Aquive]

@JorisPostNL this is running since november. Any updates?? If I knew it would take this long I had fixed all the issues myself. Some kind of ETA would be great to have...

[JorisPostNL]

Hi @Aquive we will be releasing this Monday barring any unforeseen circumstances!

Kind regards
Joris - PostNL

[Aquive]

Hey @JorisPostNL thats great news, although I will save the cheering when the moment is actually there. Thanks.

[JorisPostNL]

Hi @Aquive we have just released version 1.3.2 of our Hyva Checkout extension, which contains optimisation to the hyva checkout form validation. We hope this fixes all the issues you noted but if any remain please let us know and we will look into it some more.