Forum Replies Created
-
AuthorPosts
-
Yumikom
ParticipantHi Peter,
The test code is as follows
What we want to achieve
* Generate the contents of the checkbox list in the callback of test_B depending on the status of the checkbox in test_A.Defects
* When the value of test_A is retrieved in the callback of test_B, it is always false as well.<?php add_filter( 'rwmb_meta_boxes', 'example' ); function example( $meta_boxes ) { $prefix = ''; $meta_boxes[] = [ 'title' => __( 'test field group', 'example-domain' ), 'id' => 'test1', 'settings_pages' => ['custom-options'], 'fields' => [ [ 'name' => __( 'test A', 'example-domain' ), 'id' => $prefix . 'test_a', 'type' => 'checkbox', 'std' => false, 'required' => false, 'clone' => false, 'clone_empty_start' => false, ], [ 'name' => __( 'test B', 'example-domain' ), 'id' => $prefix . 'test_b', 'type' => 'checkbox_list', 'options' => test_function(), 'inline' => false, 'select_all_none' => false, 'required' => false, 'clone' => false, 'clone_empty_start' => false, ], ], ]; return $meta_boxes; }function test_function() { $value_a = rwmb_meta( 'test_A', array( 'object_type' => 'setting' ), 'custom-options' ); $optionsA = array( '1' => 'Apple', '2' => 'Orange' ); $optionsB = array( '3' => 'Cat', '4' => 'Dog' ); return $value_a ? $optionsA : $optionsB; }December 10, 2024 at 9:38 AM in reply to: Unintended auto-update crashes custom fields and causes fatal error #47146Yumikom
ParticipantHi Peter,
Thank you again for your prompt support!
We appreciate your willingness to consider enabling or disabling it.
We would like to respect your wish to hide the plugin, but we would like more freedom on the administrator's side, so it would be helpful if you could make it configurable like other plugins.Thank you.
December 7, 2024 at 7:04 AM in reply to: Unintended auto-update crashes custom fields and causes fatal error #47121Yumikom
ParticipantHi Peter,
I would like to use the standard WordPress functionality of controlling automatic plugin updates.
It is costly for an administrator to go to the trouble of putting in third party management plugins and setting up auto-updates for lots of plugins on many websites.I think the auto-update feature in the WordPress plugin list is very easy to use....
December 7, 2024 at 6:59 AM in reply to: Unintended auto-update crashes custom fields and causes fatal error #47120Yumikom
ParticipantHi Peter,
Thank you for your support!
The information you have provided is well understood.We would appreciate it if you could tell us why this situation is happening, rather than how to deal with it.
* Metabox extensions are not allowed to set automatic updates in the first place. This does not allow administrators to set it up freely.
It cannot be set and the current status is not displayed.* The Metabox extension updates itself even though the auto-update status is not displayed, so it would be best if you could show us how to stop this.
Please see the attached image for the plugin list that does not show the status.
https://ibb.co/wh9rnpFDecember 6, 2024 at 2:46 PM in reply to: Unintended auto-update crashes custom fields and causes fatal error #47115Yumikom
ParticipantHi,
One correction.
Metabox itself is operating with automatic updates stopped.December 6, 2024 at 2:41 PM in reply to: Unintended auto-update crashes custom fields and causes fatal error #47114Yumikom
ParticipantHi,
We are operating with Metabox itself deactivated, and would like to deactivate auto-updates of all related plugins such as Metabox Group and Builder. It would be best if it could be done in code.
If you could tell us how to stop automatic updates of extensions, that would be great!
Yumikom
ParticipantHi,
I looked up the compatibility behavior in PHP7 and found Symphony's polyfill.
https://github.com/symfony/polyfillI was able to load this in wp-config and get it to work successfully.
WordPress core also uses str_contains() etc., but polyfill is provided.It would be helpful if the plugin could be complemented with polyfill when using PHP8 functions.
Is it possible that the problem is that the Metabox itself is still out of date and only the MB extension has been upgraded?Yumikom
ParticipantHi,
I have the same request.I am testing the translation of posts by DeepL using Polylang's machine translation feature.
https://polylang.pro/deepl-machine-translation-now-available-for-polylang-pro/It is a very effective feature and will be useful for global dissemination of posts by our clients.
It would be very helpful if Metabox could also support this feature.
Please consider it!Best regards,
YumikomYumikom
ParticipantHi Peter,
Now that I understand your detailed advice, I will try with the enqueue function for the metabox field.
Thanks and regards,
YumikomYumikom
ParticipantHi Peter,
Yes, that is correct.
So is it completely impossible to match the block editor and fonts to the theme.json settings?
Do I need to copy the editor styles individually to get “WYSIWYG”?Yumikom
ParticipantHi Peter,
I have uploaded the images below.
https://ibb.co/PmnHWxMThe left image is displayed in sans-serif in the Gutenberg editor.
The right image is displayed in WYSIWYG TinyMCE editor with serif.In theme.json, sans-serif is specified.
Yumikom
ParticipantHi Peter,
Thank you for informing me that it has been corrected!
Yumikom
ParticipantHi Steve,
I think you can save the aforementioned once you put it behind you and use the latest version of WordPress, please try it once.
Yumikom
ParticipantHi Steve,
There is a problem with the metabox builder. I am also having trouble saving on many sites.
If the "Save field value" is turned off in the Advanced section of each field, it will not save.
This field was added suddenly in a recent version, and many fields that have existed for a long time have it turned off. Please be aware of this.
* Support said that it is ON by default if you create a new file with the latest version.We believe it is safer to set this in PHP instead of using the builder if there are many fields to support, since there could be problems related to saving with each version upgrade due to React support, etc.
Yumikom
ParticipantHi,
I have been able to recover many sites with the latest version of Metabox.
It's works fine now.
I set max_input_vars to 500k.I found an explanation below.
https://support.metabox.io/topic/cannot-apply-custom-fields-to-settings-pages/Best regardsm
Yumikom -
AuthorPosts