- This topic has 2 replies, 3 voices, and was last updated 1 year, 7 months ago by
Long Nguyen.
-
AuthorPosts
-
September 9, 2022 at 7:25 PM #38248
PASCAL Hämmerli
ParticipantMetabox AIO v.1.16.4
Using Metabox Builder for custom fields for USER.
Problems with read-only/disabled and saving values:Select field:
read-only: it is still possible to change value and save it
disabled: current value is lost after savingSelect advanced (same):
read-only: it is still possible to change value and save it
disabled: current value is lost after savingInput field also loose value after saving if "disabled".
Feature request for input/select fields:
- property "protected" or "locked" that would replace the field value with just a <div class="rwmb-input">[value]</div> or something that would prevent user to inspect/edit page html and update disable/readonly attributesSeptember 11, 2022 at 3:55 AM #38257sherwin_flight
ParticipantYou can use some JavaScript to remove the disabled attribute when you save, and then the values will be saved as expected.
But I think a read only/locked option would be great. I'm struggling with a similar issue right now as well, only with clone groups that i want to be read only.
September 11, 2022 at 9:10 PM #38260Long Nguyen
ModeratorHi,
For the select field, you can use the setting
disableto prevent the user from selecting the option and set the default value for the field to save the field value to the database. For example:[ 'name' => __( 'Select', 'your-text-domain' ), 'id' => 'select_67b3inmhfgs', 'type' => 'select', 'options' => [ 'a' => __( 'A', 'your-text-domain' ), 1 => __( '1', 'your-text-domain' ), 2 => __( '2', 'your-text-domain' ), 3 => __( '3', 'your-text-domain' ), ], 'std' => 2, 'disabled' => true, ], -
AuthorPosts
- You must be logged in to reply to this topic.