Meta Box

Something went wrong. Please try again!

Support › MB Builder › Something went wrong. Please try again!

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • December 4, 2025 at 12:21 PM #49479
    369cycle369cycle
    Participant

    After updating Matabox, when trying to modify an existing file, the message "Something went wrong. Please try again!" appears. Creating a new file does not show this message.

    December 4, 2025 at 10:53 PM #49487
    PeterPeter
    Moderator

    Hello,

    Please update Meta Box AIO to the new version 3.3.5, then clear all caches: plugin, browser, hosting, Cloudflare (if you use it) ... and recheck the issue.

    Let me know how it goes.

    December 15, 2025 at 9:19 PM #49533
    KaraKara
    Participant

    I'm still experiencing this issue - cannot edit any of the custom field groups. It loads briefly (flashes) and then I get the same error: "Something went wrong. Please try again!"

    December 15, 2025 at 9:26 PM #49534
    KaraKara
    Participant

    Oh and to note: I'm updated to MetaBox AIO 3.3.5. I tried deactivating all plugins and clearing cache etc etc. No luck. Hosting with Rocket.net if that helps.

    Don't see any errors in the log, but from the console:
    https://www.awesomescreenshot.com/image/57909569?key=07860e3136754c02df33805b351e7402

    December 15, 2025 at 10:03 PM #49535
    KaraKara
    Participant

    I think it's related to the Group field.
    In a new set of Custom Fields, I just tried to add it and was immediately hit with "Something went wrong. Please try again!".

    Please let me know how to fix ASAP. I use Groups throughout many sites and they are connected to Bricks Builder queries - I need to be able to edit them.

    Thank you.

    December 17, 2025 at 7:26 AM #49538
    KaraKara
    Participant

    Perhaps it's linked also to MetaBox AIO not recognizing my license? The license page says it's confirmed, and I just removed and re-added it to be sure. But when I look at the options for custom fields, I can't select a Tab. It says: "Tab (Premium)" and prompts me to upgrade to MetaBox AIO.

    Note: I purchased my license from AppSumo in 2021.

    December 17, 2025 at 9:59 PM #49541
    PeterPeter
    Moderator

    Hello Kara,

    Please contact us here https://metabox.io/contact/ regarding the license key issue. We will help you check it.

    Thanks.

    January 6, 2026 at 2:25 AM #49587
    JCJC
    Participant

    Hi there,

    I got the same issue. Can't edit custom field groups of type post. I always get the error: "Something went wrong. Please try again!" I can edit custom field groups of type block without problems though.

    Please advice.

    Best

    Jan

    January 30, 2026 at 6:46 AM #49694
    KaraKara
    Participant

    This issue is still happening. I was able to create a new set of custom fields earlier today, including a Group. But I cannot edit the custom field set now, nor can I create a new set that includes a new group.

    I get the same error: "Something went wrong. Please try again!"
    And two errors show in the console:
    https://www.awesomescreenshot.com/image/58557602?key=bade5115441d813ab615595613086dbe

    Deactivating all plugins, turning off cache, etc does not help.
    This is extremely disruptive - how can we fix this?

    January 30, 2026 at 4:23 PM #49697
    JCJC
    Participant

    Second that.

    January 30, 2026 at 4:29 PM #49698
    JCJC
    Participant

    Could it be the Server's PHP-Version? The problem site runs on PHP 8.4.16. Another site with PHP 8.5 I has none of that. Both run Metabox AIO 3.4.0 and WordPress 6.9.

    January 30, 2026 at 11:28 PM #49704
    KaraKara
    Participant

    This site was on php 8.1 and I just upgraded to 8.3, the problem persists.
    (My host doesn't have 8.5 yet so can't try that.)
    Also running AIO Version 3.4.0, WP 6.9.

    Theme is Bricks, but changing to default theme doesn't help.
    Hosting on Vultr HF on Cloudways.

  • Author
    Posts
Viewing 12 posts - 1 through 12 (of 12 total)
  • You must be logged in to reply to this topic.