URL and number fields more restrictive since update

Support MB User Profile URL and number fields more restrictive since updateResolved

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #20283
    EliodataEliodata
    Participant

    Hi,

    Since today we can't update a user profile without making change to all url and number fields first.

    I have this error message under number fields : "Please enter a multiple of 1."
    And this one under url field : "Please enter a valid URL."

    The data in these fields have been imported many months ago and we did not have any issue to update other user infos. Is there a way to let users update some profiles without having to change URL and number fields please ?

    #20287
    Long NguyenLong Nguyen
    Moderator

    Hi,

    Please remove the property required => true in the code or uncheck the option Required when creating/editing the field with the Builder to remove the validation of the field.
    https://share.getcloudapp.com/4gujbB6l

    #20292
    EliodataEliodata
    Participant

    Hi,

    Thank you for the fast support!
    The fields are not required.
    The content of these fields have been bulk imported (WP ALL IMPORT) 5 months ago. And we never faced this issue except since the last Metabox update.

    May be better with an image :

    https://bddfs.elledesignstudios.com/wp-content/uploads/2020/06/bad-content-fields.png

    Best regards

    #20293
    Long NguyenLong Nguyen
    Moderator

    Hi,

    For the field number, please use the settings 'step' => 'any' to allow a floating number 1,23.

    For the field url, please use the right format http://www.example.com. To get more information, please follow this document https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/url.

    #20296
    EliodataEliodata
    Participant

    Thank you again and sorry for the waste of time.

    I know the format is not good. The imported links were pointing to local server folders before beeing pasted into this database.
    But that bad format have never been an issue until the last metabox plugin update.

    We will try something else.

    Regards

Viewing 5 posts - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.