Meta Box

Error when update under Bricks Builder!

Support › General › Error when update under Bricks Builder!

Viewing 15 posts - 16 through 30 (of 32 total)
1 2 3
  • Author
    Posts
  • August 29, 2025 at 9:04 PM #48863
    Lydia CookLydia Cook
    Participant

    Hi Peter,

    Sorry but I can't let you have access because of GDPR on user information. As M. Stefano and I have the same error message and stack trace, is that not enough to identify the issue?

    Thanks

    August 29, 2025 at 9:35 PM #48864
    Lydia CookLydia Cook
    Participant

    Hi M. Stefano,

    To try and remove this being a specific plugin issue, these are the plugins I have installed:

    Donation thermometer
    DSGVO snippet for extensions leaflet map
    Email address encoder
    Events manager
    Fluent Forms
    Fluent forms pro add on pack
    Happyfiles pro
    Leaflet map
    Litespeed cache
    Meta Box AIO
    XML Sitemap Generator for Google

    Do you have any of these installed?

    Thanks.

    August 31, 2025 at 5:28 PM #48872
    m.stefano@digitaldomain.it[email protected]
    Participant

    Hi, Lydia
    Frankly, I don't think it's a conflict issue.
    In my installations, the number of plugins involved is very small and they can't interfere with the data.
    I think something is missing, and the errors should indicate what's missing.

    In any case, my plugins are:
    Automatic.css
    Complianz | GDPR/CCPA Cookie Consent
    Frames
    HappyFiles Pro
    Meta Box AIO
    Rank Math SEO

    September 1, 2025 at 8:22 PM #48881
    Lydia CookLydia Cook
    Participant

    OK, I've identified that these plugins are causing the fatal error when meta box aio is updated:

    fluent forms
    fluent forms pro
    litespeed cache

    I've never had an issue before when upgrading meta box so something in 3.0.1 has caused the problem. I would try upgrading to v3.0.0 to see if the issue occurred there but I can't find a download for it.

    September 1, 2025 at 8:30 PM #48882
    Lydia CookLydia Cook
    Participant

    I also see that the same thing has been raised at the bottom of this topic: https://support.metabox.io/topic/site-crashes-after-latest-update-2/

    My setup before upgrading to AIO v3.0.1 is:
    Wordpress: 6.8.2
    Bricks parent theme: 2.0.2
    Meta Box aio: 2.3.1
    PHP: 8.1.33
    Fluent forms/Pro: 6.1.2
    Litespeed cache: 7.4

    Ignoring versions of other plugins as these are not having any effect.

    September 1, 2025 at 9:57 PM #48883
    m.stefano@digitaldomain.it[email protected]
    Participant

    Hi Lydia,
    I'm having the same problem, but I don't have those plugins.
    I think something deeper in Metabox is impacting it.

    September 1, 2025 at 10:06 PM #48884
    m.stefano@digitaldomain.it[email protected]
    Participant

    Hi Lydia,
    I read the discussion you posted. I can confirm a bug has been identified in Metabox.
    Are you able to implement the fix now, or do you have to wait until the new version is released.

    September 2, 2025 at 7:19 PM #48888
    Lydia CookLydia Cook
    Participant

    Hi,

    The bug I believe was related to Meta Box Terms and the block editor and not related to the issues we both have (I'm not even sure ours are exactly the same). The fix was made on 14th August and 3.0.1 come out on the 21st so I assume it included that fix but still causes a fatal error (even though the site looks fine on the front and back ends).

    We need Meta Box to come back having investigated further. If they could identify the cause of the MB Terms error then they should be able to identify this one I would have thought.

    September 3, 2025 at 6:48 PM #48892
    BellulBellul
    Participant

    I got the same error mails ("Your Site is Experiencing a Technical Issue") today on several sites (not all have Bricks) when updating Meta Box 5.10.10 to 5.10.13 and Meta Box AIO 2.2.1 to 3.0.1. The mails refer to "Meta Box" and gives the message:

    An error of type E_ERROR was caused in line 214 of the file /home/xxx/wp-content/plugins/meta-box/inc/fields/media.php. Error message: Uncaught Error: Failed opening required '/home/xxx/wp-content/plugins/meta-box/inc/templates/media.php' (include_path='.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php') in /home/xxx/wp-content/plugins/meta-box/inc/fields/media.php:214

    During the update in the backend I saw no errors! And afterwards I can not see any errors in backend or frontend. Is it safe to ignore these error mails?

    WordPress-version 6.8.2
    Aktivt tema: Bricks Child Theme (version 1.1)
    Nuvarande tillägg: Meta Box (version 5.10.13)
    PHP-version 8.1.33

    Best,
    Bengt

    September 3, 2025 at 7:35 PM #48893
    m.stefano@digitaldomain.it[email protected]
    Participant

    We have the same problem and have experienced the same behaviors, but we haven't received any answers yet.
    I'm waiting.

    September 3, 2025 at 10:57 PM #48899
    PeterPeter
    Moderator

    Hello Stefano,

    I've tried to reproduce the issue with a clean installation of WordPress and Meta Box AIO 3.0.1 but I still could not see it.

    Can you please copy your site to a staging site and share the credentials via this contact form https://metabox.io/contact/ ?
    I will help you investigate the issue.

    September 9, 2025 at 6:32 PM #48952
    Lydia CookLydia Cook
    Participant

    Hi Peter,

    To help you solve this, I have removed user data from a staging copy of the website and sent you a message with the login details.

    Hope this helps,

    Lydia

    September 12, 2025 at 3:19 PM #48975
    Lydia CookLydia Cook
    Participant

    Peter,

    I've sent you a message with ftp details as requested but need an email address for the site administrator account so you will know when the upgrade fails.

    Thanks,

    Lydia

    October 6, 2025 at 4:38 PM #49089
    BellulBellul
    Participant

    Any solution yet? Is it just safe to ignore?

    /Bengt

    October 6, 2025 at 4:44 PM #49090
    m.stefano@digitaldomain.it[email protected]
    Participant

    I'm only having this problem with Bricks Builder; other sites with Oxigen aren't affected.

    I should add that once I updated with subsequent updates, the problem disappeared, and I haven't noticed any malfunctions.

    I don't know what to say; I was expecting a response from support, who should have already given me the errors reported.

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