Meta Box

Hello Alok,

Thanks for your feedback.

I will inform the development team to consider supporting a field with the post title and a clickable link in future updates. Let me know if you have any questions.

Hello,

I import your field group to my demo site, use the code below to output the radio field value but don't see any issue

$value = rwmb_meta( 'sub_header_display_radio', ['object_type' => 'setting'], 'custom_settings' );
echo $value;

echo '<br>';

$value2 = rwmb_meta( 'statut', ['object_type' => 'setting'], 'custom_settings' );
echo $value2;

screenshot https://imgur.com/XgJZHeq

Can you please copy your site to a staging site and share the admin account with me by submitting this form?
https://metabox.io/contact/

I will take a look.

Hello Shemzone,

Thanks for reaching out.

If you use a default WordPress theme and add the code to output the field value get_option( 'reglages-generaux-site' ) or rwmb_meta(), does it show the correct value show/hide in the frontend?

If so, I believe the issue comes from the Bricks theme. Let me know how it goes.

Yes, please share your site credentials by submitting this contact form https://metabox.io/contact/
I will take a look. Thanks.

Hello Alok Sharma,

Thanks for reaching out.

Do you use another plugin that customizes the admin area, like Admin and Site Enhancements (ASE)? This will set the admin menu display above the Meta Box Field group menu and cause the issue.
Or maybe it is a conflict issue with the admin menu style of WordPress.com hosting only.

Hello,

There isn't a complete solution with clear steps for any specific case when using Meta Box. However, you can refer to some tutorials in our documentation to use Meta Box to create custom fields for post types and use code or a page builder to output values in the frontend.
Here is a reference https://docs.metabox.io/tutorials/create-menu-restaurants-meta-box-elementor/

We also offer a customization service, please contact us here https://metabox.io/contact/

Thanks for your feedback.

I've informed the development team to consider supporting a filter hook to bypass the caching. Let me know if you have any questions.

Hello Jason,

Thanks for reaching out.

I've experienced the issue with the Rest API POST /wp-json/wp/v2/featured-property/{id}?_locale=user sometime ago, but I was not able to reproduce it with clear steps. There is a workaround:
- delete the custom post type
- create a new post type with the same slug
the posts that are stored in the table wp_posts won't be lost if you just delete the post type.