Forum Replies Created
-
AuthorPosts
-
Anh Tran
KeymasterHi Dan,
The issue with version 1.5.9 was fixed. Please just update it again.
Regarding the issue with the dismiss notice, please send me via contact form. I'll check it.
And what do you mean about UABB Info Box module & Meta Box?
Anh Tran
KeymasterHi,
By default, the plugin shortcode only has 3 fields: user email, password and password confirmation. To add fields to the registration form (including standard fields), please create a meta box for user profile, like this:
add_filter( 'rwmb_meta_boxes', function( $meta_boxes ) { $meta_boxes[] = [ 'title' => 'Registration', 'id' => 'your-registration', 'type' => 'user', 'fields' => [ [ 'type' => 'text', 'id' => 'first_name', 'name' => 'First Name', ], [ 'type' => 'text', 'id' => 'last_name', 'name' => 'Last Name', ], // More fields here ] ]; return $meta_boxes; } );Then include this form in the registration shortcode provided by the plugin:
[mb_user_profile_register id="your-registration"]Anh Tran
KeymasterYes, that's possible. To output the date in a different format, please use this code:
rwmb_the_value( $field_id, array( 'format' => 'F j, Y' ) );Anh Tran
KeymasterHi, to register a meta box for a custom post type, please:
- Go to Meta Box > Custom Fields, click Add New to add a new field group.
- Then add fields you want from the left panel.
- Click the tab Settings and select "Posts" in "Show for", and then select your post type below.
- Click Save Changes button
Now go back to your custom post type edit screen and you'll see the meta box appear. Enter some info and update the post.
To show the custom fields's values in the sidebar, there are 2 ways:
Anh Tran
KeymasterHi,
Can you post your full code so I can check it out?
Anh Tran
KeymasterHi Austin,
If you just enable
show_in_restparam for a CPT, it will use the default WordPress namespace, which iswp/v2. In order to use a custom namespace, you have to write a custom REST Controller (which is out of the scope of the extension). Please see here for more details.Update: In case you write a custom REST Controller, you might disable the rest support in the MB Custom Post Type extension, and add a custom code like this.
Anh Tran
KeymasterHi Dan,
I've just checked the plugin and see that the TGM Plugin Activation class doesn't show the notice for ones who have dismissed it. Can you tell the clients to click the dismiss link? It works per user, so if you have dismissed it, your client might still see it.
Anh Tran
KeymasterHi Dan,
I've just tested the MB Beaver Builder Integration and don't see any error. Can you post the code that registers meta box to check?
Anh Tran
KeymasterHi Guy,
Can you please try again? I've just re-uploaded the .zip file.
Anh Tran
KeymasterHey @mgratch, your solution is great! Thanks for posting it here for others. I completely forgot about the custom callback. Nice work!
Anh Tran
KeymasterYes, that's what the condition says. However, I think the problem might be: the value of a taxonomy is always an array (as we can select multiple terms to assign to a post). So it's not correct to says one array "in" another array. Can you try "contains" one value, and add another condition for the other value?
Anh Tran
KeymasterHello,
Can you give me more details on "get the MetaBox to tie to the Post Type and then put them into the sidebar"? Do you mean registering a meta box (with custom fields) for the custom post type and outputting the custom fields' values in the sidebar?
Anh Tran
KeymasterHi,
Do you set the
max_cloneparameter for the field? Can you post the code that registers meta box?July 9, 2018 at 9:19 AM in reply to: ✅Conditional Logic for hiding conflicts with required fields #10480Anh Tran
KeymasterHi Doug,
I'm afraid this (removing the required attribute) is the only way to resolve this. The Conditional Logic actually hides/shows elements. It does not removes them completely from the page (cause it doesn't know how to get them back).
Anh Tran
KeymasterI got it. The thing here is the plugin detects the first element that contains the condition, which is the first clone in this case.
It would be very confusing if it detects all elements and parse the conditions. The plugin can't understand whether to show "room-availability" when all clones satisfy the condition or any clone satisfy it. In this case, this is "any", but in general, there's no way to know that :(.
I think to solve this problem, please just set the first clone as the trigger for the rules.
-
AuthorPosts