Checkbox with “allow multiple” + “save in meta” error

  • Resolved jamienk

    (@jamienk)


    3 months, 2 weeks ago

    When my field type is “Checkbox” and I have “allow multiple”, then when I set “save in meta” I get the following WP Notice:

    <b>Notice</b>: Function register_meta was called <strong>incorrectly</strong>. When registering an "array" meta type to show in the REST API, you must specify the schema for each array item in "show_in_rest.schema.items". Please see <a href="[https://developer.ww.wp.xz.cn/advanced-administration/debug/debug-wordpress/">Debugging](https://developer.ww.wp.xz.cn/advanced-administration/debug/debug-wordpress/%22%3EDebugging) in WordPress</a> for more information. (This message was added in version 5.3.0.)

    Worse: my posts do not save the checkbox values (all are unchecked after save).

    My work-around was to use a repeater with select children, but this is not as good as a series of checkboxes.

    I put this as a Github issue, but thought maybe it would get more traction here

Viewing 4 replies - 1 through 4 (of 4 total)
  • nurb007

    (@nurb007)

    1 month, 3 weeks ago

    Hello,

    I’ve run into the exact same issue on my side when using a checkbox field with “allow multiple” and saving it as meta — the values not being saved.

    Did you happen to find a solution or workaround for this?

    Thanks in advance!

    Thread Starter jamienk

    (@jamienk)

    1 month, 3 weeks ago

    I think I turned it from multiple check-boxes to a repeater whose children are selects. This is not very good though

    nurb007

    (@nurb007)

    1 month, 3 weeks ago

    Ok, thank you

    Plugin Support Alex

    (@fellan91)

    1 month, 2 weeks ago

    Hello,

    Thank you for your report. We were able to reproduce the issue and prepare a fix for this pr: https://github.com/nk-crew/lazy-blocks/pull/370.
    We will update the plugin in a future release, and this issue should no longer occur.

    Regards,
    Alex

Viewing 4 replies - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.