Forum Replies Created
-
AuthorPosts
-
Anh Tran
KeymasterHi,
I'm afraid to say it's not possible at the moment. Fields must be created with Meta Box in order to work with the Group extension. Fields created by other plugins work in a different way. So, they're not compatible.
We're planning to write a conversion tool to convert fields created from other plugins to Meta Box. We haven't started it yet, because there are some higher priorities. But we'll try to do it asap.
KeymasterHi Thomas,
Glad that you have resolved this problem. If you don't mind, please share your solution (or link to the tutorial) here so others can refer if they have a similar problem.
Thanks,
AnhKeymasterI got it. The updating process for Builder is running. When it's finished, you'll see that option.
KeymasterHi,
Regarding the 1st question: I think adding restriction to the form is ok, we can do that. However, even if the form is restricted, you still need to prevent non-wanted users to access that page? What do you think about this?
Regarding the 2nd problem: all post data is processed via
wp_update_postandwp_insert_post. We don't run any sanitize feature for that. However, you can use these filters to perform an extra check.This is an interesting question and I'd love to hear your feedback.
Thanks,
AnhKeymasterUnfortunately no. We've added the requirement to create new term for taxonomy field for Meta Box. We'll work on that asap.
KeymasterHi, which field are you referring to? Have you tried dot notation?
KeymasterThanks for your bug report. We'll check it and update the extension asap.
KeymasterHi, user role is actually not supported in Conditional Logic yet. Because the user role is always fixed and can't be changed while editing, using it for conditional logic seems not convenient. Instead of Conditional Logic, you can use the MB Include Exclude extension which supports well for the user role.
KeymasterCan you please send me the code of the settings page to test?
KeymasterHello David, at the moment, the MB Custom Table still relies on the custom post types to store the post data such as post title and post content. It supports only saving custom fields in the custom tables.
We're working on an enhancement that brings more power to this extension, which allows you to store any content separately from the wp_posts table. That will include both the custom fields and post fields. But it's not ready yet and you need to wait.
Best regards,
AnhKeymasterHi,
Please try to use the following code for your 5 questions:
$value = rwmb_meta( 'how_to_use_radio_buttons' ); if ( 'button_one_selected' == $value ) { echo 'I Clicked on Radio Button One'; } elseif ( 'button_two_selected' == $value ) { echo 'I Clicked on Radio Button Two'; } elseif ( 'button_three_selected' == $value ) { echo 'I Clicked on Radio Button Three'; } elseif ( 'button_four_selected' == $value ) { echo 'I Clicked on Radio Button Four'; } elseif ( 'button_five_selected' == $value ) { echo 'I Clicked on Radio Button Five'; }Basically, it's the
if..elsestatement. You just need to check the value of the custom field and output the corresponding text.KeymasterHi,
Looks like the 1st image correct. Just a stupid question, but have you updated your code on your localhost? The remote host seems to work properly.
KeymasterHi,
Just want to let you know that the new field type
backgroundis added to Meta Box 4.13.0. Please update to use it. The announcement post with more details will come later today.Cheers,
AnhDecember 28, 2017 at 12:38 PM in reply to: Error with Custom Tables Plugin when Deleting Posts #8030KeymasterSorry for this bug. We should have updated Meta Box first, then MB Custom Table. Please update Meta Box now to have it fixed (the new version is released today).
Thanks,
AnhKeymasterHi,
I've just updated both Meta Box and Columns extension to fix this. Please update them as well.
Thanks,
Anh -
AuthorPosts