Bug (?) for read-only field for non admin-user: a workaround-solution

[paolo.kirschner]

Hi,
We use your plugin in the pro version to handle user-meta-field to customize
the user profile. User who changes his profile with the frontend form has two fields
disabled because only the administrator can change them.
When the user confirms its profile in the frontend form, these fields
disabled are cleared off even in the backend.
We suppose that the problem comes from the use of the attribute “disabled”
for the input tag that the values are not submitted with the form.

We found a workaround for this by using the “readonly” attribute of input
tag instead of “disabled”, that prevents the user from changing the input,
but the input is still submitted with the form.

For this we have modify the file
plugins/user-meta/view/pro/generateField.php on line 406 and line 426:
original code: “disabled” => isset($fieldReadOnly) ? $fieldReadOnly : null,
new code: “readonly” => isset($fieldReadOnly) ? $fieldReadOnly : null,

Please tell us if you have a better solution or if we were wrong diagnosis,
especially for future updates of the plugin

[Support]

Hello,

In fact, we have used “disable” attribute so that form data can’t submit, It was added with UMP early version when proper validation of input not fully implemented. BTW you can use readonly and new release will use readonly too.

Thanks.

[Author]

Posts