• Resolved fabbaf

    (@fabbaf)


    Hello,

    I created a custom metabox called “custom_metabox_event_location”. If I create a custom post type, use your block and save this setting, everything is working. Your metablock is showing the correct value of the metabox.

    But I created a custom template for my custom post type following this guide: https://developer.www.ads-software.com/block-editor/reference-guides/block-api/block-templates/#custom-post-types.

    The custom template is working and I added some of your metablock functions like “hideEmtpy” into my template, which you can see here:

    'template' => array(
        // Ort
        array( 'mfb/meta-field-block', array(
            'metaType' => 'postType',
            'fieldType' => 'meta',
            'fieldName' => 'custom_metabox_event_location',
            'hideEmpty' => 'true',
            'emptyMessage' => 'Kein Ort',
            'tagName' => 'p',
        ) ),            
    )

    If I create a new custom post type, everything is showing correct.

    The problem is, that if I enter no value in the metabox for “custom_metabox_event_location”, save my custom post type and then go back to the edit screen, the value for “hideEmpty” is back to “false”.

    Why isn’t this being saved? Do I have to add something to my custom post type?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Phi Phan

    (@mr2p)

    Hello @fabbaf, I think the problem is that you are using a string value for hideEmpty. You should set it as 'hideEmpty' => true instead of 'hideEmpty' => 'true'. Please try it with a real boolean value and let me know if it works.

    Phi.

    Thread Starter fabbaf

    (@fabbaf)

    Thanks for your fast reply.

    This solved my problem and I learned about string values and boolean values. Sorry for this newbie question.

    Plugin Author Phi Phan

    (@mr2p)

    You’re welcome, @fabbaf.

    Have a nice day!

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘hideEmpty value in custom post type template not being saved’ is closed to new replies.