Forum Replies Created
-
AuthorPosts
-
February 13, 2018 at 10:43 AM in reply to: Conditional logic not working with clones in groups #8539
Anh Tran
KeymasterI got it. The problem is the cloning "radio" field. I've fixed it here. Please try and let me know how it goes.
Thanks
KeymasterHi Martin,
Sorry for the confusion. The Builder extension is behind some extensions and we're updating it to catch the others. Specifically:
- The validation module has not yet been added to the Builder. You can do that via the Custom Attributes for meta box (via the Settings tab) like this:
https://imgur.elightup.com/MQsvIfq.png
It's not intuitive yet. But it should works (you can verify by seeing the exported Code). Here is the guide to work with custom attributes (written for field settings, but also works for meta box settings).
- Regarding "Why could MB Frontend not allow in the visual interface to select post_title and post_excerpt", my first attempt to build the extension is to make it also work with existing meta box in the backend, where post fields already exist. Adding post fields to the form will duplicate them in the backend. So, they must be removed somehow.
Anyway, can you send me an admin account to check why the code doesn't work via contact form?
Thanks,
AnhKeymasterI found the problem. The Conditional Logic applies CSS (
display: block) inline to the field, which overwrites the CSS of the Group extension (collapsed state). I've just updated the Group extension. Please try and let me know how it goes.KeymasterPlease add the validation rules to the meta box code exported from the Builder extension. Here is the code:
And the code to show form is just:
$form = '[mb_frontend_form id="question" post_fields="title" submit_button="Submit Question" confirmation="Thank you for submitting your question, which will be addressed shortly!"]'; echo do_shortcode( $form );KeymasterI checked on Windows with XAMPP and didn't see this bug. Probably the PHP version. Which version are you using?
Anyway, I've just added a fix for that. We're working on some other issues and will release the new version when it's done.
KeymasterHi Martin,
You can add validation rules for post title, just like normal custom fields:
$meta_boxes[] = [ 'title' => 'Simple form', 'id' => 'simple-form', 'fields' => [], // Your fields 'validation' => [ 'rules' => [ 'post_title' => [ 'required' => true, 'minlength' => 5, ], ], ], ];See more validation rules.
KeymasterHello,
First of all, thank you for trying Meta Box. I'm sorry that you had difficulties using it. Can you please clarify your concerns so that I can help you more closely? For example: what fields do you want to create, with what conditions, or which part of the documentation is vague? I will try my best to help you.
I see you bought only the Builder extension. There are some features such as conditional display meta boxes for a specific page template or display it for terms, and they need some other extensions to work. Besides, the approach in the Builder extension is somewhat different from ACF, so maybe something is not the same.
I hope you can give us the chance to help you.
Thank you.
KeymasterI guess we have some misconception about "template". The template that plugin provides is the "text" version of the meta box settings, which is different from the page template that you imagine in the frontend. Am I correct?
KeymasterOh, I see. My previous reply was for another problem (show/hide the image/video field when selecting an option). I'll check this bug and reply soon.
KeymasterHello,
Yes, you can. Just create different meta boxes for different pages. You might want to use the MB Include Exclude to show specific meta boxes for a specific page. This extension works well with the MB Template extension.
KeymasterHello,
Your question is about the Frontend Submission extension, so I moved it to the corresponding forum.
Regarding the HTML markup of uploaded images, we mimic the markup in the Media Library in the admin area, which looks like this:
https://imgur.elightup.com/WimQaQC.png
Although there are some redundant
div, it doesn't affect your style very much. However, you still need to add some CSS to make it looks seamless with your theme.KeymasterPlease check the field ID in the code. I didn't know which
$prefixyou used, so I usefootball_. Not sure if that's right.Anyway, do not just copy and paste the code 😉
February 7, 2018 at 12:02 PM in reply to: Php Error conflicts with Tribulant Newsletter Plugin #8480KeymasterNo problem. New version with hot fix released.
KeymasterHi, I've just tested the code. Sometimes the bug occurs, sometimes doesn't. I'll keep tracking on that.
KeymasterHi,
I've just checked your code and found that the problem is the ID of the radio field, which is
type. As this is the radio field, there are actually 2 inputs with the same name. The JavaScript tries to *guess* the field using this selector[name*="type"]. It's ambiguous, and actually it returns *another WordPress field*, which is thepost_type(a hidden input).I'd suggest using prefix for your field's ID (as stated in the documentation). It's a good way to keep the field ID/name unique, and thus make the selector works. I've tried changing the ID from
typetotype123and it works.Please try and let me know how it goes.
-
AuthorPosts
