Meta Box

"Something went wrong. Please try again!" when opening Custom Field Group

Support › MB Builder › "Something went wrong. Please try again!" when opening Custom Field GroupResolved

Viewing 15 posts - 16 through 30 (of 39 total)
1 2 3
  • Author
    Posts
  • November 19, 2025 at 5:29 AM #49374
    michaeltsherry@gmail.com[email protected]
    Participant

    I'm having the same issue after updating.

    November 19, 2025 at 5:47 AM #49375
    Michael KernMichael Kern
    Participant

    To everyone saying they’re getting the same “Something went wrong. Please try again” message:

    As soon as this happens, open Chrome DevTools, then copy-paste the entire contents of the Console to pastebin and link here.

    My bet is that it’s the React JS having issues of some sort.

    November 19, 2025 at 5:27 PM #49376
    eden22eden22
    Participant

    Same issue here -> trying to add a group field and "Something went wrong. Please try again!"

    Console error logs:

    ReferenceError: Cannot access 'o' before initialization
    at Module.default (4988.app.js:1:123)
    at c (react.min.js?ver=18.3.1.1:10:2391)
    at Wn (react-dom.min.js?ver=18.3.1.1:10:35439)
    at e (react-dom.min.js?ver=18.3.1.1:10:39675)
    at fr (react-dom.min.js?ver=18.3.1.1:10:54704)
    at hr (react-dom.min.js?ver=18.3.1.1:10:56142)
    at Qs (react-dom.min.js?ver=18.3.1.1:10:123734)
    at wl (react-dom.min.js?ver=18.3.1.1:10:88341)
    at bl (react-dom.min.js?ver=18.3.1.1:10:88269)
    at yl (react-dom.min.js?ver=18.3.1.1:10:88132)
    ar @ react-dom.min.js?ver=18.3.1.1:10
    a.componentDidCatch.t.callback @ react-dom.min.js?ver=18.3.1.1:10
    at @ react-dom.min.js?ver=18.3.1.1:10
    Jr @ react-dom.min.js?ver=18.3.1.1:10
    Zr @ react-dom.min.js?ver=18.3.1.1:10
    Gr @ react-dom.min.js?ver=18.3.1.1:10
    (anonymous) @ react-dom.min.js?ver=18.3.1.1:10
    xl @ react-dom.min.js?ver=18.3.1.1:10
    fl @ react-dom.min.js?ver=18.3.1.1:10
    Nn @ react-dom.min.js?ver=18.3.1.1:10
    (anonymous) @ react-dom.min.js?ver=18.3.1.1:10
    react-dom.min.js?ver=18.3.1.1:10 TypeError: Cannot read properties of null (reading 'removeEventListener')
    at A.hasUnsavedChanges (app.js?ver=8c07b96bef0c1b5a19b8:1:243564)
    at Or (react-dom.min.js?ver=18.3.1.1:10:72846)
    at Ir (react-dom.min.js?ver=18.3.1.1:10:73032)
    at El (react-dom.min.js?ver=18.3.1.1:10:92118)
    at fl (react-dom.min.js?ver=18.3.1.1:10:85253)
    at Nn (react-dom.min.js?ver=18.3.1.1:10:32442)
    at react-dom.min.js?ver=18.3.1.1:10:82952

    No reply from dev team for 3 weeks is quite concerning

    November 20, 2025 at 7:03 PM #49389
    SébastienSébastien
    Participant

    All "Custom Fields" return this error (but it is not blocking):

    deprecated.min.js?ver=e1f84915c5e8ae38964c:2 Bottom margin styles for wp.components.ToggleControl is deprecated since version 6.7 and will be removed in version 7.0. Note: Set the__nextHasNoMarginBottomprop to true to start opting into the new styles, which will become the default in a future version.

    The blocking error "Something went wrong. Please try again!" is triggered (in my case) with all "Custom Fields" that contain "Groups" (in version 3.3.2, everything worked normally in version 3.3.1):

    i @ deprecated.min.js?ver=e1f84915c5e8ae38964c:2
react-dom.min.js?ver=18.3.1.1:10 ReferenceError: Cannot access 'o' before initialization
    at Module.default (4988.app.js:1:123)
    at c (react.min.js?ver=18.3.1.1:10:2391)
    at Wn (react-dom.min.js?ver=18.3.1.1:10:35439)
    at e (react-dom.min.js?ver=18.3.1.1:10:39675)
    at fr (react-dom.min.js?ver=18.3.1.1:10:54704)
    at hr (react-dom.min.js?ver=18.3.1.1:10:56142)
    at Qs (react-dom.min.js?ver=18.3.1.1:10:123734)
    at wl (react-dom.min.js?ver=18.3.1.1:10:88341)
    at bl (react-dom.min.js?ver=18.3.1.1:10:88269)
    at yl (react-dom.min.js?ver=18.3.1.1:10:88132)
ar @ react-dom.min.js?ver=18.3.1.1:10
react-dom.min.js?ver=18.3.1.1:10 TypeError: Cannot read properties of null (reading 'removeEventListener')
    at A.hasUnsavedChanges (app.js?ver=8c07b96bef0c1b5a19b8:1:243564)
    at Or (react-dom.min.js?ver=18.3.1.1:10:72846)
    at Ir (react-dom.min.js?ver=18.3.1.1:10:73032)
    at El (react-dom.min.js?ver=18.3.1.1:10:92118)
    at fl (react-dom.min.js?ver=18.3.1.1:10:85253)
    at Nn (react-dom.min.js?ver=18.3.1.1:10:32442)
    at react-dom.min.js?ver=18.3.1.1:10:82952
ar @ react-dom.min.js?ver=18.3.1.1:10

    However, after fiddling with the console, I realized that the error would disappear on its own when the cache was emptied.

    Conclusion: no more React errors when correctly refreshing the problematic Custom Fields pages in the MB Builder.

    Hoping it lasts! 😉

    November 20, 2025 at 9:24 PM #49391
    PeterPeter
    Moderator

    Hello,

    You can download the previous version of Meta Box AIO 3.2.0 here
    https://www.dropbox.com/scl/fi/bb75smqepzl7ig1w361sp/meta-box-aio-3.2.0-1.zip?rlkey=g5kkcnbhjabdmv1q4qax48l6q&st=djas5kb0&dl=0

    I've tried to reproduce the issue or import some field groups of other users but I didn't see that on my site. Maybe it is a caching issue. Please try to clear all caches (plugin, browser, hosting ...) or even deactivate/reactivate Meta Box plugins and recheck the issue.

    December 1, 2025 at 11:01 PM #49444
    MotiveinkMotiveink
    Participant

    Is there still no solution?

    December 1, 2025 at 11:05 PM #49445
    MotiveinkMotiveink
    Participant

    https://pastebin.com/205ZqP1e

    December 1, 2025 at 11:06 PM #49446
    MotiveinkMotiveink
    Participant

    I disabled and re-enabled the plugin, but the problem remains.

    December 1, 2025 at 11:13 PM #49448
    MotiveinkMotiveink
    Participant

    I share the server settings

    Architettura del server Linux 5.15.0-131-generic x86_64
    Server web nginx/1.27.1
    Versione di PHP 8.1.33 (supporta valori a 64bit)
    PHP SAPI fpm-fcgi
    Variabile PHP max input 15000
    Limite di tempo PHP 30
    Limite di memoria PHP 512M
    Max input time 100
    Dimensione massima di upload dei file 512M
    Dimensione massima del post PHP 512M
    Versione di cURL 7.68.0 OpenSSL/1.1.1f
    SUHOSIN è installato? No
    La libreria Imagick è disponibile? No
    I permalink in chiaro sono supportati? Sì
    robots.txt Il sito utilizza il file dinamico robots.txt generato da WordPress.
    Orario attuale 2025-12-01T16:11:40+00:00
    Orario UTC attuale Monday, 01-Dec-25 16:11:40 UTC
    Orario attuale del server 2025-12-01T17:11:39+01:00

    December 2, 2025 at 1:36 AM #49451
    SébastienSébastien
    Participant

    Hi Motiveink (+Peter and everyone else!)

    Have you tried forcing a refresh and clearing the cache (CTRL+F5 on PC), or checking the Console > Network > Disable cache option?

    It might also be worth checking if any cache plugins on your website are causing issues. That worked for me - good luck! 😉

    December 2, 2025 at 5:49 PM #49455
    MotiveinkMotiveink
    Participant

    I do not have cache enabled and the problem persists.

    December 2, 2025 at 5:53 PM #49456
    MotiveinkMotiveink
    Participant

    Same website, if I go back to version 3.2.0, everything is fine, the custom fields work.

    December 2, 2025 at 6:21 PM #49457
    SébastienSébastien
    Participant

    So sorry to hear that... :-/
    I know how stressful this can be.

    Have you tried going to the custom field group that's no longer working, opening your browser's DevTools (Chromium - F12), enabling "Disable cache" in the Network tab, and then refreshing the page?

    December 2, 2025 at 7:20 PM #49458
    MotiveinkMotiveink
    Participant

    Thank you! I made a video, it seems that it doesn't work even when I disable the cache.

    https://www.dropbox.com/scl/fi/crvyg81fl8zvlvaz0hsj7/Registrazione-schermo-2025-12-02-alle-13.18.12.mov?rlkey=u18ta3u7y6co1tkppuqduk96g&dl=0

    December 2, 2025 at 10:32 PM #49461
    PeterPeter
    Moderator

    Hello Motiveink,

    Please share your site admin account by submitting this contact form https://metabox.io/contact/
    I will take a look.

    Thank you.

  • Author
    Posts
Viewing 15 posts - 16 through 30 (of 39 total)
1 2 3
  • You must be logged in to reply to this topic.