Forum Replies Created
-
AuthorPosts
-
November 13, 2022 at 10:01 PM in reply to: ✅Function WP_Object_Cache::get was called incorrectly #39112
Peter
ModeratorHello Alaan,
Thank you for your feedback. There are some changes in the new version of WordPress 6.1 and it might cause the issue. I will inform the development team to update our plugin to adapt to these changes.
Peter
ModeratorI don't see the error 400 on my end when trying to add some terms Best Season to a post, screen record https://monosnap.com/file/kAw6x5Xk3FOQpLQ0wbVW9fPuTdOpRz
November 13, 2022 at 9:38 PM in reply to: Issues displaying blog post author name and comment counts #39108Peter
ModeratorHello,
On the single post page, no need to use this loop
{% for post in query.posts %}it should be used on the archive page to display posts.
Peter
ModeratorHello,
Can you please deactivate all plugins except Meta Box and MB extensions, switch to a standard theme of WordPress (2022) and recheck this issue? If the quicktags work on the backend, they should work on the frontend also.
Peter
ModeratorHello Lucas,
In case of using Oxygen Builder, WP Grid Builder, please reach out to them if you have any issues with installation, configuration, compatibility, or usage.
Refer to our support policy https://metabox.io/support/topic/support-policy/
Peter
ModeratorHello Michael,
The helper function can help you to output the field value anywhere on the site, the main goal is to pass the field ID and post ID to the function, like this
<?php $value = rwmb_meta( 'my_custom_field', '', $post_id ) ?>You can contact WooCommerce support or your theme support to ask for getting the post ID when using the hook.
November 13, 2022 at 6:08 PM in reply to: ✅Warning: Illegal string offset 'parent' after last update #39103Peter
ModeratorHello Hans,
Then you should contact The Events Calendar support to ask for further assistance. If you experience that issue again, you can enable the WP Debug log and share it here. I will help you to investigate the issue.
Peter
ModeratorHello Mike,
If you want to get the field value, please use the helper function rwmb_meta(), for example
$field = rwmb_meta( 'mh_website_name', ['object_type' => 'setting'], 'site-settings' ); echo ($field);The helper function rwmb_get_field_settings() helps you to get the field settings like name, type, id ..., not the field value.
Peter
ModeratorI understand the issue, in the admin area, WordPress does not support displaying 2 fields with the same ID on a page. In the frontend, with the frontend submission form, it works properly.
In this case, I recommend removing the standard featured image section of WordPress to show the custom field created by Meta Box. If you create the CPT by Meta Box, you can go to Meta Box > Post Type > Edit the post type > Support tab > Disable option "Thumbnails".
Peter
ModeratorHello Yasmine,
Can you please share the code that creates the custom fields on your site? I recommend using this code to output a variable if you do not know what could be the value.
echo "<pre>"; print_r( $variable ); echo "</pre>";Peter
ModeratorIf you want to get the post meta, you need to use the function get_posts().
Regarding the custom avatar field, can you please let me know how did you register the custom field and the code that output the field value?
Peter
ModeratorNot yet, the development team is working on this issue. I will let you know when it is fixed.
Peter
ModeratorHello Denise,
Please follow these steps to create and use the template for your CPT
1. When registering the CPT, enable the option
Page attributesin the Supports tab.2. Create a template file with the CPT slug in the file name. For example, CPT slug:
job
file name: template-job.php
content<?php /* Template Name: Job Template Post Type: job */ get_header( 'review' ); ?> content here ... <?php get_footer();Peter
ModeratorHello Sascha,
When creating the CPT, on the tab Support, you can disable the option
Editoror use this custom PHP code to remove the content area of a post/post type// Remove the editor. Change 'post' to your custom post type. add_action( 'init', function () { remove_post_type_support( 'post', 'editor' ); } );Get more details on the WordPress documentation https://developer.wordpress.org/reference/functions/remove_post_type_support/
November 11, 2022 at 9:53 PM in reply to: Open Street Map (Custom Style) not visible on frontend #39077Peter
ModeratorHello there,
To display a map subfield in a group with the custom style, you need to use the PHP code, the Twig code in the View is not supported in this case. Refer to this topic https://support.metabox.io/topic/using-a-open-street-map-with-an-address-text-field-inside-a-group/
-
AuthorPosts