Default value get replaced after last update

Hello @stefanp44 ,

I’ve checked this issue on my lab site and I wasn’t able to replicate that. The required number field with 0 as the default value was correctly submitted.
I also checked this on your site and I wasn’t able to replicate this issue – did you downgrade to the previous version?
In case you downgrade, please share the exported form (on pastebin.com)
https://wpmudev.com/docs/wpmu-dev-plugins/forminator/#import-export

kind regards,
Kasia

Hi Kasia (@wpmudev-support2),

Yes, I did downgrade on this prod website, but went on testing on a staging website, same issue.
Here’s the pastebin link: https://pastebin.com/eDhE58S9
Please check the nubmer-6 field, you’ll see the problem (also works with number-11, number-12 and number-16 fields): there’s an indication text filled and a default value as well, set to 0.

Kind regards,

Hi @stefanp44

Thank you for response and sharing the form!

I can see the issue and replicate it on my own test site with your form.

Interestingly, I still cannot replicate this with a form that I created there from scratch – with number field set exactly the same way (same limits and default value, same placeholder text, similar conditional visibility and so on).

I admit it’s quite strange but despite a lot of testing, I couldn’t find out what’s causing it.

I have asked our developers for consultation on it so they’ll check it and we’ll update you here with more information once we got feedback from them.

Kind regards,
Adam

Hi Adam (@wpmudev-support8),

Thank you for your reply. Indeed, it is strange. I hope the dev team will find a solution, because I don’t see myself rebuild all the forms from scratch after an update ;-).

Best regards,

Hi @stefanp44

I hope so too!

Meanwhile I got information about a workaround that should do the trick for now. You would need to change format of all number fields to be like this

1234567.89

(so no spaces and a dot as a decimal separator)

and keep that format set consistently across all the fields. It seems to be working in our tests.

Best regards,
Adam

Hi Adam (@wpmudev-support8),

Thanks for the trick, it works indeed. Faster than rebuilding the form too! ??
Still, it would be interesting to understand why it acted like this.

Best regards,

Hi @stefanp44

Our developer found that the issue is related to inputmask library, https://github.com/RobinHerbots/Inputmask/issues/2502 we reported this to our developers and I hope we can apply a workaround to bypass this problem.

We can’t give an estimated time but you can follow the Forminator updates on https://wpmudev.com/roadmap/#forminator

Best Regards
Patrick Freitas

Hi Patrick (@wpmudevsupport12),

It’s great already that the related problem has been found. I can wait for the update regarding this issue as the bypass works, I am actually glad that I could help point it out.

Best regards,