Broken after update? Meta-Box Builder 4

This topic has 14 replies, 3 voices, and was last updated 3 years, 11 months ago by Yumikom.

Viewing 15 posts - 1 through 15 (of 15 total)

Author

Posts
January 29, 2021 at 8:36 PM #24246

jw_bln
Participant

For me the same:
Creating new field-groups in UI is possible.
But as soon as you change something later or you trash/restore it will misbehave (e.g. conditional logic not working) or even not showing up in admin.
Seems different people having issues with the new version...

In case of not showing the fields in the Admin-UI the following error is existing:
react-dom.min.js?ver=16.13.1:125 TypeError: Cannot read property 'controls' of undefined
at app.js?ver=4.0.0:13
at we (react-dom.min.js?ver=16.13.1:84)
at zj (react-dom.min.js?ver=16.13.1:226)
at Th (react-dom.min.js?ver=16.13.1:152)
at tj (react-dom.min.js?ver=16.13.1:152)
at Te (react-dom.min.js?ver=16.13.1:146)
at react-dom.min.js?ver=16.13.1:61
at unstable_runWithPriority (react.min.js?ver=16.13.1:25)
at Da (react-dom.min.js?ver=16.13.1:60)
at Pg (react-dom.min.js?ver=16.13.1:61)

How long will a fix need - maybe it's better to go back to the older version until all is tested correctly?
I found the changelog: https://metabox.io/plugins/meta-box-aio/changelog/
But where I can find the download of the pre-versions?

Best regards

Add New Note to this Reply

January 30, 2021 at 11:11 PM #24269

Long Nguyen
Moderator

Hi,

Can you please follow the first step of Debugging Information?
https://support.metabox.io/topic/how-to-create-a-new-topic/

Then clear the browser cache and check this issue again. You can also share a screen record or screenshots when manipulating the field groups, I will try to reproduce the issue on my end.

Add New Note to this Reply

March 26, 2021 at 6:06 PM #26727
Yumikom
Participant
I am in great trouble.
I have the same problem.

When I edit the data created in the original old builder and save it in the new builder, nothing is displayed. I'm at a loss.

There are a lot of errors in Jacascript.

All I edited was to add a piece of this custom field that specifies a specific fixed page ID in the conditional logic.
This site is multi-site.

Looks like a very incomplete program.
```
custom-admin-style.css:1 Failed to load resource: the server responded with a status of 404 (Not Found)
jquery-migrate.min.js?ver=3.3.2:2 JQMIGRATE: Migrate is installed, version 3.3.2
post.js?ver=4.1.0:7 Uncaught DOMException: Failed to execute 'querySelector' on 'Document': '#2020-12-17-815 .handle-actions' is not a valid selector.
    at addIcon (https://example.net/wp-content/plugins/meta-box-builder/assets/js/post.js?ver=4.1.0:7:26)
    at Array.forEach (<anonymous>)
    at https://example.net/wp-content/plugins/meta-box-builder/assets/js/post.js?ver=4.1.0:13:38
    at https://example.net/wp-content/plugins/meta-box-builder/assets/js/post.js?ver=4.1.0:14:4
react-dom.min.js?ver=16.13.1:125 TypeError: Cannot read property 'controls' of undefined
    at app.js?ver=4.1.0:13
    at we (react-dom.min.js?ver=16.13.1:84)
    at zj (react-dom.min.js?ver=16.13.1:226)
    at Th (react-dom.min.js?ver=16.13.1:152)
    at tj (react-dom.min.js?ver=16.13.1:152)
    at Te (react-dom.min.js?ver=16.13.1:146)
    at react-dom.min.js?ver=16.13.1:61
    at unstable_runWithPriority (react.min.js?ver=16.13.1:25)
    at Da (react-dom.min.js?ver=16.13.1:60)
    at Pg (react-dom.min.js?ver=16.13.1:61)
Me @ react-dom.min.js?ver=16.13.1:125
app.js?ver=4.1.0:13 Uncaught (in promise) TypeError: Cannot read property 'controls' of undefined
    at app.js?ver=4.1.0:13
    at we (react-dom.min.js?ver=16.13.1:84)
    at zj (react-dom.min.js?ver=16.13.1:226)
    at Th (react-dom.min.js?ver=16.13.1:152)
    at tj (react-dom.min.js?ver=16.13.1:152)
    at Te (react-dom.min.js?ver=16.13.1:146)
    at react-dom.min.js?ver=16.13.1:61
    at unstable_runWithPriority (react.min.js?ver=16.13.1:25)
    at Da (react-dom.min.js?ver=16.13.1:60)
    at Pg (react-dom.min.js?ver=16.13.1:61)
custom-admin-style.css:1 Failed to load resource: the server responded with a status of 404 (Not Found)
```
Add New Note to this Reply
March 26, 2021 at 6:32 PM #26728

Yumikom
Participant

Hi,

It seems that the path where wordpress is installed is different, which is displayed in the Javascript error. In fact, I'm installing in a directory instead of the document root.

Best regards,
Yumikom

Add New Note to this Reply

March 26, 2021 at 9:23 PM #26733

Long Nguyen
Moderator

Hi Yumikom,

If you've upgraded MB Builder from version 3.x to 4.x and the field groups disappear, please follow this note to force migrating fields again https://docs.metabox.io/extensions/meta-box-builder/#upgrade.

Add New Note to this Reply

March 27, 2021 at 7:10 AM #26738

Yumikom
Participant

Hi,

When I saved the json that exported the original unbroken Custom fieled, all the Settings values disappeared.

Furthermore, even if you set and save Settings again, the settings are not saved at all. No matter how many times you do it.

I also tried the Upgrade URL that was sent to me, but nothing happened and nothing changed.

I'm having trouble with so many projects being adversely affected, please tell me how to avoid builder glitches, such as reverting to an older builder.

Best regards,
Yumikom

Add New Note to this Reply

March 27, 2021 at 9:42 PM #26747

Long Nguyen
Moderator

Hi,

Please export the field groups (JSON file) then share them here. I will try to import it to my local site to check the issue.

Add New Note to this Reply

March 28, 2021 at 1:28 PM #26765

Yumikom
Participant

Hi Long,

It contains customer-specific field names and cannot be published here.
If possible, I would like to pass the file directly by e-mail etc., so please let me know a good way.

Best regards,
Yumikom

Add New Note to this Reply

March 28, 2021 at 9:56 PM #26772

Long Nguyen
Moderator

Hi,

Please share the information via this contact form https://metabox.io/contact/, I will help you to check it.

Add New Note to this Reply

April 1, 2021 at 6:23 PM #26865

Long Nguyen
Moderator

Hi Yumikom,

Please update the newest version of MB Builder 4.1.2 or MB AIO 1.13.7 to fix the issue. Let me know how it goes.

Add New Note to this Reply

April 1, 2021 at 7:13 PM #26868

Yumikom
Participant

Hi Long,

I tested it in an updated state. However, when I saved it, the Conditional Logic conditions were no longer determined, and the bug that the Settings state returned to the default was not fixed and the situation did not change.

Best regards,
Yumikom

Add New Note to this Reply

April 21, 2021 at 2:45 PM #27448

Yumikom
Participant

Hi,

Is it expected that the problem that the data of the old builder is corrupted by automatic plugin updates and the conditional logic does not work can be fixed?

Many of my clients use Metabox. I feel that I need to be prepared to withdraw the builder from all sites. Unfortunately, this bug gives me a huge amount of work. I have to make a schedule.

Please let us know if you can fix this bug or if it is safer to remove the builder from all sites.

Best regards,
Yumikom

Add New Note to this Reply

April 22, 2021 at 10:12 PM #27523

Long Nguyen
Moderator

Hi Yumikom,

Please update the newest version of Meta Box extensions or MB AIO 1.13.8 and re-check the issue. You might also need to increase the PHP settings value by following this article https://metabox.io/wordpress-custom-fields-not-saving-increase-max-input-vars/

Add New Note to this Reply

April 26, 2021 at 5:29 PM #27654

Yumikom
Participant

Hi Long,

I tested the behavior with the new builder and the conditional logic didn't work at all.
Detailed information was sent by email. Please tell me what I can do about this bug.

Thanks and regards,
Yumikom

Add New Note to this Reply

April 26, 2021 at 6:35 PM #27660

Yumikom
Participant

One good news.

I was able to confirm that the problem that all the settings data became the default when saving was fixed.

Thank you for your continued support for the problem of conditional logic.

Thanks and regards,
Yumikom.

Add New Note to this Reply
Author

Posts

Viewing 15 posts - 1 through 15 (of 15 total)

You must be logged in to reply to this topic.