Your form is not valid, fix which error ?

Hello and thanks a lot. I had noticed your test going through, and I think you may have solved the issue.

Your test went through, but like you hadn’t entered any data at the query for the childrens’ birthdates. This lead me to pay closer attention to this field, and I’ve realized now that the form rejects applications with children birthdates in the format ##.##.#### (this leads to the error), but accepts them in the format ##/##/#### (or with no birthdate, in both cases the test goes through).

I have now to specify to the users which format to use when they’re typing the date in, or to find a parameter allowing for more flexible input. But this is a trivial issue, now that it’s been identified. [edit: done and tested, it’s ok now]

So thank you again. I wouldn’t have pinpointed the problem without your test. We can consider the issue solved now.

[Edit too : in my relief, I had typed this after your test had highlighted the source of the problem, and only skimmed through your actual post because I am dumb and considered the problem gone, but I realize that there is indeed an ongoing problem with the date picker that is supposed to spare the users having to type the date themselves… I had just forgotten it was a thing. In my defense, my skull is currently filled with cement due to a bad flu, and this doesn’t really help cognitively.

Anyway, the current solution of having people type the date following an indicated format is good enough, even with the mystriously absent datepicker. I might investigate further, and familiarize myself with staging plugins, but the most pressing aspect being solved, this can thankfully wait for my brain’s de-petrification. Thank you once more for your precious help.]

• This reply was modified 1 year ago by perastika. Reason: better re-read

Everything is working sufficiently well for the users, as they can now type the birthdates following the displayed format.

What nags me a bit is that, indeed, one feature seems broken : if I understand well, clicking on the field should pop up a little visual calendar (the date picker). Its absence isn’t an issue in practice, as the users don’t know what should or shouldn’t be appearing, and don’t require it to use the form. But it still means that something is secretely dysfunctioning, and I don’t like letting things in that (let’s say technically “solved” but “unresolved”) state.

I’ll investigate further, checking if there’s a conflict with some other plugin (anti-spam sentry, etc). And I might come back if I’m stumped. But none of that affects the practical use of the website, so in that sense, the trouble is solved.