Forum Replies Created
-
AuthorPosts
-
Peter
ModeratorThe issue happens when the setting max number of clones set to 1 and if we set it to 2 or more, the setting
clone_empty_startwill work properly. The issue has been escalated to the development team, it will be fixed in the next update of our plugins.Thank you.
Peter
ModeratorHello,
Please share your site admin account by submitting this contact form https://metabox.io/contact/
I will take a look.Peter
ModeratorHello,
I change the code from
{% set user_id = mb.get_current_user_id() %}to
{% set user_id = mb.get_queried_object_id() %}to get the current query user ID and it shows the user (author) info correctly. Just a WordPress function to get the user ID, not an issue of MB Views or Meta Box.
January 10, 2025 at 10:53 PM in reply to: Empty cloneable date field give critical WordPress error in PHP8.1 #47368Peter
ModeratorHello Wirat,
I'm not able to reproduce the issue on my site. I can save an empty value for the cloneable datetime field. Can you please try to change the field ID to another one and save the post again?
If it still doesn't work, please export the field group to a JSON file and share it here. I will help you check the issue.
Following the documentation https://docs.metabox.io/extensions/meta-box-builder/Peter
ModeratorHello,
You need to install and activate the plugin MB Columns to show the columns option in the builder
https://metabox.io/plugins/meta-box-columns/January 10, 2025 at 10:34 PM in reply to: Unintended auto-update crashes custom fields and causes fatal error #47366Peter
Moderator>> Has it been improved in the latest version and can it be enabled/disabled at will?
Not yet. The development team is working on it and this feature will be included in future updates of Meta Box plugins.
Thank you.
Peter
ModeratorHello,
Thanks for your feedback. I see that when enabling SCRIPT_DEBUG, there is a warning message in the Console tab of the browser and that might cause the issue. Let me escalate the issue to the development team to check it.
Peter
ModeratorStrangely, I still receive no information regarding this topic in the ticket system. Can you please submit the contact form again?
Peter
ModeratorHello,
I'm not using Bedrock, just the standard WordPress installation with 2021 theme and I don't see that issue with WP 6.7.1.
Can you try with a simplified environment and recheck the issue?January 9, 2025 at 8:28 PM in reply to: MB jQuery Validation - Scroll To Highlight Error - file_upload - Issue #47352Peter
ModeratorHello,
Thanks for the feedback. I can reproduce the issue from scratch. I've escalated this issue to the development team to fix the jQuery validation and improve the behavior to scroll to the error message.
January 9, 2025 at 8:06 PM in reply to: Unintended auto-update crashes custom fields and causes fatal error #47350Peter
ModeratorHello,
>> Only for Metabox related extension plugins, if I set “auto-update enabled”, I can't change the setting in the plugin list.
Can you please let me know which extension plugin you set auto-update enabled? And share some screenshots or screen record of the issue on your site.
January 8, 2025 at 11:10 PM in reply to: MB jQuery Validation - Scroll To Highlight Error - file_upload - Issue #47345Peter
ModeratorHere is the "Required" field setting https://imgur.com/INH8uRy
it is available for all fields. And I see that it is scrolling to the error message when submitting the post.Peter
ModeratorHello Yumiko,
The column setting is available in the builder, see this screenshot https://imgur.com/0NxOW8U
If not, please let me know the MB Builder plugin version and MB extension plugins activated on your site. I will help you check the issue.
Peter
ModeratorHello,
It looks like the subfield value has been saved to the database and the first clone entry is displayed. You can try to access the database, table wp_postmeta and doublecheck this.
If there is a field value of the field group, delete them all and recheck the clone entry.Peter
ModeratorHello,
>> Can you provide use cases why someone would use taxonomy_advanced over taxonomy?
In some cases, you have to use the
taxonomy_advancedfield: subfield in a group or field in a block. Because thetaxonomyset post terms so it won't work in those cases.Besides that, when you want to save the field value as post meta instead of post term, you will use the field
taxonomy_advanced.You can read this article as a reference https://metabox.io/custom-fields-vs-custom-taxonomies/
-
AuthorPosts