Forum Replies Created
-
AuthorPosts
-
[email protected]
ParticipantThanks for the support, this worked for me.
ParticipantSorry for my mistake in trying to import a Settings Page into a Post Type.
Everything works perfectly.Perhaps I'll use a header in the files to generate an alert that the wrong import type is being used...
For distracted people, like me in this case.Sorry again.
ParticipantI'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.
ParticipantWe have the same problem and have experienced the same behaviors, but we haven't received any answers yet.
I'm waiting.ParticipantHi 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.ParticipantHi Lydia,
I'm having the same problem, but I don't have those plugins.
I think something deeper in Metabox is impacting it.ParticipantHi, 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 SEOParticipantYes, I read the reply.
I'm trying. My problem is replicating the error.
From what I understand, this happens when it updates, then it stops giving you any more signals.
If you read this thread, there's another user who reported the same problem.ParticipantIn another installation with a different server, without any sort of scripts, with version 3.0 this did not occur.
At the time of the update...Versione di WordPress 6.8.2
Tema attivo: Bricks Child Theme (versione 1.1)
Plugin corrente: Meta Box AIO (versione 3.0.1)
Versione PHP 8.3.24Dettagli dell'errore
====================
Un errore di E_ERROR è stato causato nella linea 214 del file /var/www/vhosts/domain.it/httpdocs/wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box/inc/fields/media.php. Messaggio di errore: Uncaught Error: Failed opening required '/var/www/vhosts/domain.it/httpdocs/wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box/inc/templates/media.php' (include_path='.:/opt/plesk/php/8.3/share/pear') in /var/www/vhosts/domain.it/httpdocs/wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box/inc/fields/media.php:214
Stack trace:
#0 /var/www/vhosts/domain.it/httpdocs/wp-content/plugins/meta-box-aio/vendor/meta-box/meta-box/inc/fields/image-advanced.php(79): RWMB_Media_Field::print_templates()
#1 /var/www/vhosts/domain.it/httpdocs/wp-includes/class-wp-hook.php(324): RWMB_Image_Advanced_Field::print_templates()
#2 /var/www/vhosts/domain.it/httpdocs/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#3 /var/www/vhosts/domain.it/httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action()
#4 /var/www/vhosts/domain.it/httpdocs/wp-includes/media-template.php(1584): do_action()
#5 /var/www/vhosts/domain.it/httpdocs/wp-includes/class-wp-hook.php(324): wp_print_media_templates()
#6 /var/www/vhosts/domain.it/httpdocs/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#7 /var/www/vhosts/domain.it/httpdocs/wp-includes/plugin.php(517): WP_Hook->do_action()
#8 /var/www/vhosts/domain.it/httpdocs/wp-admin/includes/template.php(2222): do_action()
#9 /var/www/vhosts/domain.it/httpdocs/wp-admin/update.php(53): iframe_footer()
#10 {main}
thrownParticipantHi Peter
I figured out what was causing the error.
I found this script for adding an avatar to WordPress a while ago, and it's part of my default installation. Now, it seems to have become incompatible for some reason./** * Custom Avatar */ add_filter( 'get_avatar_url', 'mb_get_avatar_url', 10, 3 ); function mb_get_avatar_url( $url, $id_or_email, $args ) { if ( is_numeric( $id_or_email ) ) { $user_id = $id_or_email; } elseif ( is_string( $id_or_email ) && ( $user = get_user_by( 'email', $id_or_email ) ) ) { $user_id = $user->ID; } elseif ( is_object( $id_or_email ) && ! empty( $id_or_email->user_id ) ) { $user_id = (int) $id_or_email->user_id; } if ( empty( $user_id ) ) { return $url; } $custom_avatar = rwmb_meta( 'custom_avatar', [ 'object_type' => 'user' ], $user_id ); if ( ! $custom_avatar ) { return $url; } $url = $custom_avatar['full_url']; return $url; }The script requires a custom field
<?php // Displaying uploaded image: ?> <?php $image = rwmb_meta( 'custom_avatar', [ 'object_type' => 'user', 'size' => 'thumbnail' ], get_current_user_id() ); ?> <h3>Logo</h3> <img src="<?php echo $image['url']; ?>"> <?php // or simpler: ?> <h3>Logo</h3> <?php rwmb_the_value( 'custom_avatar', [ 'object_type' => 'user', 'size' => 'thumbnail' ], get_current_user_id() ) ?>It would be helpful if we could use it again.
But I can't fix it.ParticipantI use the single Meta Box plugin on my sites.
This error is common on all sites I've updated to version 3.0.1 of Meta Box AIO.ParticipantThanks for the support.
I've verified that the field definitions are now visible again and figured out what did create the problem.ParticipantCiao Peter
After creating a new parallel admin account (to send you the login credentials), I realized that logging in with the new credentials did not cause the problem.I am now sending you both sets of credentials, so you can verify for yourself.
At this point the problem started on my administration account and this doesn't make me feel comfortable for all the other installations I have.
ParticipantParticipantOperations and tests done
First part
All PTs and CFs cancelled
uninstalled Metabox plugins
Checked in FTP if there were spurious folders or files
restarted the serversecond part
Metabox plug-ins re-installed
imported PT and CF definitionsnothing to do, everything as before...
So I did something that I should have done immediately, install a version of Meta Box AIO earlier than 1.19.1 luckily I had an old version of AIO 1.16.4 which once replaced the current one solved the situation.
The really strange thing is that I did a test by importing all PT and CF on a different installation of a machine that I use for tests and experiments and there with Meta Box AIO 1.19.1 installed everything works as I expect.
It seems clear to me that the problem at this point lies in the AIO module and how it now deals with field definitions.
If it can be useful, I could create an admin account on this installation to debug, in the meantime I've done a backup, so it can be manipulated at will.
-
AuthorPosts