Forum Replies Created
-
AuthorPosts
-
Lydia Cook
ParticipantI just updated a fresh staging copy with Meta Box AIO 2.8.3 to have AIO v3.2 and still got the error reported.
This is really annoying as I set up three weeks ago a staging copy for Peter of Metabox to do the upgrade and see the error and I've received no response from him as to whether he did upgrade and determined what the issue is.
Come on Meta Box, this issue is now causing quite a few of us an issue and we can't upgrade. I would have expected this to have been resolved by now.
Lydia Cook
ParticipantPeter,
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
Lydia Cook
ParticipantHi 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
Lydia Cook
ParticipantHi,
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.
Lydia Cook
ParticipantI 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.4Ignoring versions of other plugins as these are not having any effect.
Lydia Cook
ParticipantOK, I've identified that these plugins are causing the fatal error when meta box aio is updated:
fluent forms
fluent forms pro
litespeed cacheI'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.
Lydia Cook
ParticipantHi 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 GoogleDo you have any of these installed?
Thanks.
Lydia Cook
ParticipantHi 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
Lydia Cook
ParticipantIgnore the last two posts as this is after update. Checking my live site running pre v3 the folder and lines are there.
Lydia Cook
ParticipantAlso I only have 206 lines in the media.php file.
Lydia Cook
ParticipantWhen I look at the error line "Failed opening required '/home/staging1/wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box/inc/templates/media.php'" and check my installation, there is no templates folder.
Lydia Cook
ParticipantDespite the error message, the Meta Box AIO plugin got upgraded to v3.0.1 (according to the version in plugins) and I'm seeing no fatal issues with the website. I can't restore my staging site at the moment I'm afraid to upgrade Meta Box again as I'm currently testing other things.
Lydia Cook
ParticipantI've just updated my staging site to 3.0.1 which is built using Bricks and I have the same issue. I have no custom avatar code. I only have Meta Box AIO installed.
Error Details
=============
An error of type E_ERROR was caused in line 214 of the file /home/staging1/wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box/inc/fields/media.php. Error message: Uncaught Error: Failed opening required '/home/staging1/wp-content/plugins/meta-box-aio/vendor/meta-box/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/staging1/wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box/inc/fields/media.php:214
Stack trace:
#0 /home/staging1/wp-includes/class-wp-hook.php(324): RWMB_Media_Field::print_templates()
#1 /home/staging1/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#2 /home/staging1/wp-includes/plugin.php(517): WP_Hook->do_action()
#3 /home/staging1/wp-includes/media-template.php(1584): do_action()
#4 /home/staging1/wp-includes/class-wp-hook.php(324): wp_print_media_templates()
#5 /home/staging1/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#6 /home/staging1/wp-includes/plugin.php(517): WP_Hook->do_action()
#7 /home/staging1/wp-admin/includes/template.php(2222): do_action()
#8 /home/staging1/wp-admin/update.php(53): iframe_footer()
#9 {main}
thrownOctober 19, 2023 at 12:06 AM in reply to: ✅Show author in post list without adding support for author #43559Lydia Cook
ParticipantHi Peter,
Many thanks, this worked like a charm.
Lydia
Lydia Cook
ParticipantOK so the only benefit I can see is that if you had multiple taxonomy fields in one CPT all pointing to the same custom taxonomy, then if these fields were of the regular taxonomy type, all chosen values would be set the same after saving, whereas if they were all of the taxonomy advanced type, all the selections would be preserved as the data is saved into the postmeta.
Not sure why you would have multiple taxonomy fields in a CPT pointing to the same custom taxonomy though. -
AuthorPosts