If the required fields are not set on user profile's save, every field's value will be dropped

[jackjohansson]

Hi,

In the user profile screen, there are some required fields such as email and nickname.

Let's say I have added some extra fields using edit_user_profile and show_user_profile action hooks. These fields are filled by the user, and do not have to be required.

If the user fills every field (let's say 20 fields, took 10 minutes to fill) but clears the email field and save the form, there will be shown an admin error:

ERROR: Please enter an email.

Every field that was filled by the user will be dropped, and has to be refilled.

The point is, until the required fields are empty, there is no reason to let the user save the form in the first place.

This issue has been discussed in the WordPress Development StackExchange. I've posted 3 solutions for this issue, which can be improvement or bug resolve.

Below is a link to the question on WPSE. I would be happy to write an accurate solution, in case the development team decides to push this into their future patches.

​https://wordpress.stackexchange.com/q/272940/94498

King regards,
Jack

[swissspidy]

This could be as simple as using the validateForm() JavaScript function available in WordPress.

[jackjohansson]

Replying to swissspidy:

This could be as simple as using the validateForm() JavaScript function available in WordPress.

Thanks for the reply.

However, shouldn't this be a part of the core by default? There's no point in submitting a form that lacks required fields.

It would make some sense if the form was properly saved, but it's just submitted in order to trigger an error.

[swissspidy]

Replying to jackjohansson:

Replying to swissspidy:

This could be as simple as using the validateForm() JavaScript function available in WordPress.

Thanks for the reply.

However, shouldn't this be a part of the core by default? There's no point in submitting a form that lacks required fields.

It would make some sense if the form was properly saved, but it's just submitted in order to trigger an error.

I didn't oppose your idea. By pointing out validateForm() I'm simply suggesting a way to solve this in core.

[SergeyBiryukov]

Related: #27606

[jackjohansson]

Replying to SergeyBiryukov:

Related: #27606

Hi,

The related ticket purposes a patch on the server side. However the issue is still standing (see the linked question).

Is a front-end solution possible in this case as @swissspidy mentioned? I've already coded a script that validates the form before sending (including extra fields added by user). If so, should I push it forward?

[psykro]

Replying to jackjohansson:

Replying to SergeyBiryukov:

Related: #27606

Hi,

The related ticket purposes a patch on the server side. However the issue is still standing (see the linked question).

Is a front-end solution possible in this case as @swissspidy mentioned? I've already coded a script that validates the form before sending (including extra fields added by user). If so, should I push it forward?

I'd say if you have a patch that solves the problem, go ahead and submit it

[jackjohansson]

First patch for user update, has one bug currently

[jackjohansson]

I've added the initial patch for this bug. It checks nickname and password in the by jQuery, and the email by AJAX.

Currently it has a bug, you need to click the submit button twice if all of the fields are valid. There is most likely some other handler interfering, as this bug doesn't exist in a JSFiddle version of this patch.

If anyone has a moment to try it out, their feedback will be greatly appreciated.

@swissspidy @SergeyBiryukov @psykro @afercia

[psykro]

Thanks @jackjohansson I'll take a look

[DrewAPicture]

Assigning to mark the good-first-bug as "claimed".

[SergeyBiryukov]

Related: #47064