Forum Replies Created
-
AuthorPosts
-
Yumikom
ParticipantHi Long,
We are satisfied with the prompt response.
I will try to export it.Thanks,
YumikomYumikom
ParticipantHi,
I feel the same way.I'm in great trouble because I can't export / import the project under renovation to production right now.
The export / import function is really important for updating live site.
Best regards,
YumikomYumikom
ParticipantHi,
There is no problem because publish is extracted from the acquired data.
Thank you.
Yumikom
ParticipantHi Long,
It would be helpful if I could use query to get the post.
This is because post_status is very important throughout WordPress.
I have high expectations for the future.Thanks and regards,
YumikomDecember 29, 2020 at 5:30 PM in reply to: ✅Unable to read multibyte text in code output by the builder #23759Yumikom
ParticipantHi Tran,
Thank you for your prompt response!
I will try it in the next update.
Maintaining the ease of use of the builder is very helpful to me.Thanks,
YumikomDecember 21, 2020 at 10:04 AM in reply to: ✅Unable to read multibyte text in code output by the builder #23658Yumikom
ParticipantHi Long,
Thank you for teaching me that it is difficult to treat tone accents as text.
I often use the process of creating complex custom fields in MB Builder and customizing them in PHP.
It was very difficult to manually enter the name, group title, add title...etc. field, so it would be helpful if we could generate a code that was ready to use as before.Thanks and Regards,
YumikomDecember 20, 2020 at 2:02 PM in reply to: ✅Unable to read multibyte text in code output by the builder #23644Yumikom
ParticipantHi,
On the admin panel edit page,'##' is displayed.
I'm using it on a'page'that has Gutenberg disabled.'name' => "###\xe3\x83\xa1\xe3\x82\xa4\xe3\x83\xb3\xe3\x82\xb9\xe3\x83\xa9\xe3\x82\xa4\xe3\x83\x89\xe3\x82\xb7\xe3\x83\xa7\xe3\x83\xbc###",'###メインスライドショー###'
I want to edit with plain text in the code.
Best regards,
YumikoYumikom
ParticipantHi,
I have to add the required validation function to the items that have already been created in MB Builder, and please tell me which file should be changed to change the message.I wish I had a translation file ...
Best regards,
YumikoYumikom
ParticipantHi Long,
Thank you for your support as soon as possible.
It would be helpful if this feature could also be set in MB Builder,
so I hope to see more features in the future.Thanks and Regards,
YumikomYumikom
ParticipantHi,
It is solved!
I generate options like the article below, it seems to work.
https://docs.metabox.io/fields/select-advanced/Thank you.
Yumikom
ParticipantHi Anh,
Thank you for your teaching about Outside condition.
I solved what I wanted to do!Thanks!
February 25, 2020 at 9:12 PM in reply to: ✅Field conditional logic doesn't work with Gutenberg #18408Yumikom
ParticipantHi Anh,
I'm always thankful for your support.
I was relieved to support post_type rule.
I use this condition a lot.As you suggested, I tried with simple settings.
But again, the condition is not working in Gutenberg, which is fine in the classic editor.With the following settings, I want this field to be displayed only when post_type is 'page', but it will be displayed in 'post', 'page' and 'general'.
add_filter( 'rwmb_meta_boxes', 'your_prefix_register_meta_boxes' ); function your_prefix_register_meta_boxes( $meta_boxes ) { $prefix = ''; $meta_boxes[] = array ( 'title' => esc_html__( 'test', 'text-domain' ), 'id' => 'test', 'post_types' => array( 0 => 'post', 1 => 'page', 2 => 'general', ), 'context' => 'normal', 'priority' => 'high', 'fields' => array( array ( 'id' => $prefix . 'post_mnfi92e2ko', 'type' => 'post', 'name' => esc_html__( 'Post', 'text-domain' ), 'post_type' => array( 0 => 'page', ), 'field_type' => 'select_advanced', 'visible' => array( 'when' => array( array ( 0 => 'post_type', 1 => '=', 2 => 'page', ), ), 'relation' => 'and', ), ), ), ); return $meta_boxes; }Thanks and Regards,
YumikoFebruary 24, 2020 at 9:24 AM in reply to: ✅Field conditional logic doesn't work with Gutenberg #18379Yumikom
ParticipantHi,
I'm using Metabox for many years. A license is also bought every client.
This condition was used so far, and it was no problem. It can't be used in Gutenberg.
Please support post_type as a field condition even for posts using Gutenberg.
I'm having trouble getting Metabox in the classic editor I've used up to now to be able to migrate to Gutenberg.Regards,
YumikoJanuary 24, 2020 at 9:46 AM in reply to: ✅Clone file field in group is not displayed on edit page #17995Yumikom
ParticipantHi Anh,
I was able to update the builder plugin to the latest and confirmed it was fine.
Thank you!January 24, 2020 at 9:31 AM in reply to: ✅Clone file field in group is not displayed on edit page #17994Yumikom
ParticipantHi Anh,
The test code is below.
$meta_boxes[] = array ( 'title' => esc_html__( 'test', 'text-domain' ), 'id' => 'test', 'post_types' => array( 0 => 'post', ), 'context' => 'normal', 'priority' => 'high', 'fields' => array( array ( 'id' => $prefix . 'group_test', 'type' => 'group', 'name' => esc_html__( 'Group', 'text-domain' ), 'fields' => array( array ( 'id' => $prefix . 'test1', 'type' => 'file_advanced', 'name' => esc_html__( 'File Advanced', 'text-domain' ), 'max_file_uploads' => 1, 'max_status' => false, 'clone' => 1, 'sort_clone' => 1, ), ), 'clone' => 1, 'sort_clone' => 1, 'default_state' => 'expanded', ), ), ); return $meta_boxes;Thanks and Regards,
Yumikom -
AuthorPosts