Forum Replies Created
-
AuthorPosts
-
Yumikom
ParticipantHi Peter,
Thank you for building the test site so many times!
Thanks to your support, I figured out the cause.
When I used AI generation to write a report form with a large number of fields, the readonly syntax was incorrect.After checking the syntax on your test site and adjusting it, the readonly + hide_from_front fields were successfully saved without being deleted, retaining their stored values.
Thanks and regards,
YumikoYumikom
ParticipantHi,
Previously, I mentioned read-only fields where values disappear upon saving in the frontend. After prolonged use, the checkbox in the save field remains permanently unchecked.
Regarding this save field, as previously reported, unless the default behavior is changed, critical customer data is being destroyed daily, causing significant issues.
→ Due to frequent problems, the plugin's auto-update feature has been disabled.The issue in this thread pertains to the hide_from_front, so we kindly ask for your continued cooperation.
Yumikom
ParticipantHi Peter,
I didn't receive any notification, so I missed the weekend and the validity period expired. A slightly longer validity period would be helpful.
Currently, in another case, the value of the readonly attribute in Metabox is being saved as an empty value during editing.
This is a bug report concerning the post editing screen, and we plan to investigate it immediately. WP5.8 + Metabox is version 5.4.6.
Yumikom
ParticipantHi Peter,
Thanks for your constant support!
Since the values keep disappearing in my environment, please allow me to review the code on your demo site.July 22, 2025 at 9:36 AM in reply to: Unintended auto-update crashes custom fields and causes fatal error #48594Yumikom
ParticipantHi Tran,
I always appreciate your plugins.
I have been asking for this for a while now, but is it difficult to achieve the display of update settings for extended plugins?
The rectangle in the following image shows the function of the area enclosed by the rectangle.
Only Metabox, unlike other plugins, does not follow WordPress core functionality.
https://ibb.co/wrgnz1qsIf we decide not to support this, we will be forced to stop updating plugins throughout.
There have been a number of collapses of the Metabox functionality, and the prime contractor is working on an emergency response plan.We are currently looking into measures to minimize the damage to the corporate site as much as possible. We would like to continue to recommend metabox, so please let us know how you plan to handle this issue.
Thanks and regards,
YumikomJuly 12, 2025 at 2:36 PM in reply to: Unintended auto-update crashes custom fields and causes fatal error #48557Yumikom
ParticipantHi Tran,
>> Has it been improved in the latest version and can it be enabled/disabled at will?
Another client's site crashed.
Somehow, could you please return the WordPress core standard to be configurable in individual plugins, in line with the specification, so that the automatic updates of extended plugins can be freely stopped and enabled?Many client sites continue to collapse and are very difficult to deal with.
Any help you can provide would be greatly appreciated.Best regards,
YumikoMay 28, 2025 at 12:20 PM in reply to: Unintended auto-update crashes custom fields and causes fatal error #48334Yumikom
ParticipantHi Anh,
I have always been very grateful to Meta Box and your support.
The Meta Box that was giving me errors had automatic updates disabled since last year's update. It is not that old.
We would appreciate it if you could provide a final resolution to the issue regarding automatic updates.May 27, 2025 at 12:27 PM in reply to: Unintended auto-update crashes custom fields and causes fatal error #48327Yumikom
ParticipantHi,
In this case, only the extension has been updated again without my permission, and due to a version difference with Metabox, I get a PHP error and can no longer edit the site.
It was the following error, which has been resolved after updating the Metabox itself.
Fatal error: Uncaught Error: Undefined constant "RWMB_CSS.The extensions do not show the auto-update enabled/disabled, they are all listed in the “disabled” list, but they are being updated on their own.
Is there any plan to address this?
It's a fatal glitch and I'd appreciate it if you could address it as soon as possible.
The inability to view or control the auto-update enable/disable settings for each MB plugin does not seem to match the WordPress plugin specifications.
Best regards,
YumikomYumikom
ParticipantHi Peter,
I see, I need the Columns plugin, thank you!
January 14, 2025 at 11:13 AM in reply to: Unintended auto-update crashes custom fields and causes fatal error #47399Yumikom
ParticipantHi Peter,
Wow! I am glad to hear that you are working on the functional modifications.
Thank you for everything you do!Yumikom
ParticipantHi Peter,
Thanks again for your support!
Attached is a screen that does not show the columns input field.
builder is 4.9.7January 10, 2025 at 8:10 AM in reply to: Unintended auto-update crashes custom fields and causes fatal error #47358Yumikom
ParticipantHi Peter,
Thank you for your support.
The situation is as reported in this thread.
I don't see the “Enable Automatic Updates” message, so I can't change it back to “Disabled”.
Is this issue not addressed in the latest version?
I would like to know the status of this issue.Has it been improved in the latest version and can it be enabled/disabled at will?
January 8, 2025 at 10:04 AM in reply to: Unintended auto-update crashes custom fields and causes fatal error #47333Yumikom
ParticipantHi Peter,
Is it possible to solve this problem too?
Only for Metabox related extension plugins, if I set “auto-update enabled”, I can't change the setting in the plugin list.
We think this is clearly a very inconvenient bug and would appreciate it if you could fix it.
I would like to get rid of this problem somehow, as the site breaks down due to auto-update many times.
Thanks again for your cooperation.
Yumikom
ParticipantHi peter,
It could be obtained with get_options().
Thank you for sharing this information.It would be helpful if you could also mention in the document that rwmb_meta() is not available in callback.
Thanks again.
Yumikom
ParticipantHi,
The defect is not related to the name of the settings ID.
It is the correct setting in my code.I am specifying Metabox for the Settings page configured in the code below.
define( 'SETTINGS_OPTION_NAME', 'custom-options' ); function com_options_page( $settings_pages ) { $settings_pages[] = array( 'id' => SETTINGS_OPTION_NAME, 'option_name' => SETTINGS_OPTION_NAME, 'menu_title' => 'サイト設定', 'icon_url' => 'dashicons-edit', 'style' => 'no-boxes', 'columns' => 1, 'position' => 2, ); return $settings_pages; } add_filter( 'mb_settings_pages', 'com_options_page' );I make sure that $value_a is always false.
Can you please confirm the behavior of this bug? -
AuthorPosts