Forum Replies Created
-
AuthorPosts
-
Peter
ModeratorHello Oscar,
This issue has been fixed and included in version 2.1.6 of MB Custom Table and 1.20.3 of MB AIO.
You can read more about the changelog here https://metabox.io/plugins/meta-box-aio/changelog/
August 29, 2024 at 10:43 PM in reply to: AIO 1.30.0: Uncaught Error: Undefined constant "MBB\\RWMB_CSS_DIR" #46288Peter
ModeratorHello Ryan,
Do you install and activate the plugin Meta Box? The constant
RWMB_CSS_DIRis defined in the Meta Box file wp-content/plugins/meta-box/inc/loader.phpIf you already activated Meta Box and still see the issue, please try to deactivate all plugins except Meta Box, MB AIO, switch to a standard theme of WordPress and check the issue again.
August 29, 2024 at 10:35 PM in reply to: Please FIX ! Visible condition NOT WORK after upgrade to Meta Box 5.10.0 #46287Peter
ModeratorHello,
Thanks for your details. There is an issue with the cloneable field in the new version of Meta Box. I can reproduce the issue on my demo site and I've escalated this to the development team. It should be fixed in the next update of our plugins.
You can remove the cloneable option of the field to use the conditional logic in the meantime.August 29, 2024 at 10:16 PM in reply to: Metabox Image Advanced: Warning: Array to string conversion #46285Peter
ModeratorHello Lee,
Thank you for sharing the field group. I can reproduce the issue on my demo site and I've escalated this to the development team. It should be fixed in the next update of our plugins.
You can remove the cloneable option of the field and add some new images to the field > save the post to remove the error message.Peter
ModeratorHello Yasmine,
I'm sorry about the experience you have. We acknowledge that there is an issue with the cloneable group field in the new version. You can try to use version 1.29.0 on your site and check the issue again.
August 28, 2024 at 10:35 PM in reply to: Please FIX ! Visible condition NOT WORK after upgrade to Meta Box 5.10.0 #46272Peter
ModeratorHello,
Please export the field group to a JSON file and share it here. I will check the issue on my demo site. I re-test the issue with two simple text fields and see that the visible conditional logic still works properly.
Following the documentation https://docs.metabox.io/extensions/meta-box-builder/#export--import
Peter
ModeratorHello Bertus,
The default value of the range field is 1, according to the documentation https://docs.metabox.io/fields/range/
I will inform the development team to fix the default value in the builder.Peter
ModeratorThank you for sharing the solution.
Peter
ModeratorHello,
There is an issue with the subfield in the cloneable group and our development team is working to fix this. The fix will be included in the new version of our plugins.
Thanks for your patience.
August 27, 2024 at 11:25 PM in reply to: Metabox Image Advanced: Warning: Array to string conversion #46264Peter
ModeratorHello Lee,
Can you please share some screenshots of the field on the editing page? And please export the field group to a JSON file then share it here. I will import it to my local site and recheck the issue.
Following the documentation
https://docs.metabox.io/extensions/meta-box-builder/#export--importPeter
ModeratorHello,
No, that doesn't work like that. You need to add tabs to one field group "meta-box-id-1" and add this ID to the frontend shortcode.
If you add more field group IDs to a frontend shortcode, they will be displayed in separate sections (from top to bottom) in the frontend.August 27, 2024 at 6:34 AM in reply to: ✅Create a custom field that pulls the values from a field of a settings page #46256Peter
ModeratorHello Henri,
If you want to use a field value on a settings page as the choice of a select field, you will need to use the code to register the field. Here is an example
https://support.metabox.io/topic/dynamically-populate-the-options-of-a-select-custom-field-base-on-global-cf/#post-42765If you also want to update the field on the post after updating the field on the settings page, you can use the action hook
rwmb_after_save_field
Please follow the documentation https://docs.metabox.io/actions/rwmb-after-save-field/Peter
ModeratorHello Michael,
Please share your site admin account by submitting this contact form https://metabox.io/contact/
I will take a look.Peter
ModeratorHello Nick,
There isn't an option to hide (exclude) the field in the frontend by using the shortcode attributes like that. If you want to hide a field in the frontend, please enable the option "Hide from front end" in the builder https://docs.metabox.io/extensions/mb-frontend-submission/#hiding-a-field
Peter
ModeratorHello Michael,
I import the JSON file to my demo site and I can upload a single image as well. On your site, it could be a conflicting issue with another plugin or theme. You can try to deactivate all plugins except Meta Box, MB extension plugins, switch to a WordPress theme and check the issue again.
-
AuthorPosts