Forum Replies Created
-
AuthorPosts
-
Peter
ModeratorHello Tanja,
Each relationship box has the ID
{$relationship_id}_relationships_fromand{$relationship_id}_relationships_to. You can include these IDs in the form shortcode to show it on the front end.For example:
[mb_frontend_form id="meta-box-id-1,posts-to-page_relationships_from" post_fields="title,content"]Following the documentation https://docs.metabox.io/extensions/mb-frontend-submission/#how-to-add-relationships-to-the-frontend-submission-form
ModeratorHello Topher,
The compatibility plugin between Meta Box and WP All Import (WPAI) is developed by WPAI team. Please use their plugin to get full features when importing data with Meta Box.
https://www.wpallimport.com/import-meta-box-fields/ModeratorHello,
Can you please export the field group to a JSON file and share it with me? I will import the field group to my demo site, check the field settings and see how it works on my site.
Following the documentation https://docs.metabox.io/extensions/meta-box-builder/#export--import
ModeratorHello,
All the post type settings are stored in the post content, there is nothing to do with the custom field of the post type
mb-post-type. Please check this screenshot https://imgur.com/ZZ7nHx7you can update the post type settings by updating the post content of the post type
mb-post-type.If you want to get and update the post content of a post type, you have to include
editorin thesupportsarray for the content field to be included in the REST API response.Here is an example
function enable_rest_api_for_metabox_post_type($args, $post_type) { if ($post_type === 'mb-post-type') { $args['show_in_rest'] = true; $args['supports'] = ['title', 'editor']; } return $args; }however, when you edit the post type in the admin area, the UI will be broken because
editoris enabled by customization.ModeratorHello,
Yes, it is possible. WordPress supports a filter hook
register_post_type_argsso you can modify a post type setting. Please follow the documentation
https://developer.wordpress.org/reference/hooks/register_post_type_args/ModeratorHello Oliver,
Each view template is a post, stored in the table wp_posts. If you want to access the view post via Rest URL, you can modify the post type
mb-views, and enable Rest API for this post type'show_in_rest' => trueThen you can access the view post with the URL format:
https://site.com/wp-json/wp/v2/mb-views/post-id-123Refer to this topic https://wordpress.stackexchange.com/questions/342540/is-there-possible-way-to-modify-custom-post-type
and documentation https://developer.wordpress.org/reference/hooks/register_post_type_args/ModeratorHello Alex,
The issue in this topic has been resolved. However, your issue with the custom block and select_advanced field isn't fixed. We are still researching this issue and working on it. The fix for that issue will be included in future updates.
In the meantime, you can follow the workaround from our user in this topic to fix the issue
https://support.metabox.io/topic/bug-with-select_advanced-fields/#post-47857Thank you.
March 27, 2025 at 10:39 PM in reply to: ✅Need to have colon : in a custom select field - Escaping characters? #47940ModeratorHello,
If you use the builder to create the custom field, you need to use the format
value: Labelfor the select option. For the label, you can add any characters there. For example:red1: Red: 1 red2: Red: 2 red3: Red: 3Please check this screenshot https://imgur.com/eVoleqB
ModeratorHello,
I import the field group to my demo site and see that the WYSIWYG subfield is not a cloneable field. So the correct code to output this field value is
$groups = rwmb_meta( 'konc_sku_pol' ); foreach ( $groups as $group ) { // Field konc_sku_pol_txt: $wysiwyf_field = $group[ 'konc_sku_pol_txt' ] ?? ''; echo do_shortcode( wpautop( $wysiwyf_field ) ); }Let me know if it helps.
ModeratorYes, that's it. I've also escalated this issue to the development team to check and fix it in future updates.
Thank you.
ModeratorHello Tom,
Can you please export the field group to a JSON file and share it here? I will check the field settings and help you correct the code to output the WYSIWYG subfield value.
Refer to the documentation https://docs.metabox.io/extensions/meta-box-builder/#export--importMarch 26, 2025 at 11:07 PM in reply to: Wysiwyg sanitization - allow nothing but what I define #47927ModeratorHello Duffl,
Sorry for the late reply. The WYSIWYG field uses
wp_kses_postfunction for sanitization. You can also create your own custom function to sanitize the field value.
Please follow the documentation https://docs.metabox.io/sanitization/
https://github.com/wpmetabox/meta-box/blob/master/inc/sanitizer.php#L85March 26, 2025 at 11:03 PM in reply to: Feature Request: Add Gesture Handling Support for Open Street Maps Field #47925ModeratorHello Pawel,
Thanks for your feedback.
I will forward this topic to the development team to consider supporting the GestureHandling feature for future updates.
ModeratorHello Tanja,
I'm afraid that MB Frontend Submission doesn't support duplicating posts in the frontend. You can use a third-party plugin and duplicate the posts in the admin area.
ModeratorHello,
After importing the field group https://pastebin.com/kTVMJ7GE to my demo site, I can see the issue.
This happens with the total columns in the first tab, the total columns of custom fields should be equal 12 or a multiple of 12.
If I remove the last custom field in the first tab, then it works properly. Please check this screenshot https://imgur.com/dRExMgt
Let me know if it works on your site.
-
AuthorPosts