Hi @fuzzybo
I hope you are doing well today.
Each site is for sure different as it possibly uses different plugins or themes. In the WP repository, there are over 60,000 plugins, and some of them possibly exist on that site. Taking this into account, with each update (Hummingbird or other plugins) there is a risk of new potential conflicts.
Would you please run a conflict test? Please deactivate all plugins except Hummingbird one and check if the problem is gone. If so, then enable all plugins one by one and find which one is having a conflict. If there is no positive result, switch to the default WordPress theme like 2019, and see if it works.
Before this test, we recommend full site backup or running this test on the staging site.
Kind Regards,
Kris
Hello there,
since the update to Hummingbird 3.8.0 our client expirienced errors and was blocked from logging into the backend on his 3 diverse WordPress installation, all using the Hummingbird plugin. We couldn’t reproduce the issue from our location though.
When trying to log in, they get an error message “There was a critical error on your website…” in the Frontend and the folloging error log entry in our server’s error.log file [paths and domains cut for security reasons]:
2024/04/30 11:32:37 [error] 14668#14668: *1328752 FastCGI sent in stderr: “PHP message: PHP Warning: Undefined array key “wphb” in /var/[PATH…]web/wp-content/plugins/hummingbird-performance/admin/class-admin.php on line 469PHP message: PHP Fatal error: Uncaught TypeError: array_filter(): Argument #1 ($array) must be of type array, null given in /var/[PATH…]/web9/web/wp-content/plugins/hummingbird-performance/admin/class-admin.php:472
Stack trace:
#0 /var/[PATH…]/web/wp-content/plugins/hummingbird-performance/admin/class-admin.php(472): array_filter()
#1 /var/[PATH…]/web/wp-includes/class-wp-hook.php(324): Hummingbird\Admin\Admin->wphb_style_upgrade_pro_upsell()
#2 /var/[PATH…]/web/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters()
#3 /var/[PATH…]/web/wp-includes/plugin.php(517): WP_Hook->do_action()
#4 /var/[PATH…]/web/wp-admin/admin-header.php(163): do_action()
#5 /var/[PATH…]/web/wp-admin/index.php(137): require_once(‘…’)
#6 {main}
thrown in /var/[PATH…]/web/wp-content/plugins/hummingbird-performance/admin/class-admin.php on line 472″ while reading response header from upstream, client: [AN IP-ADRESS…], server: [DOMAIN…], request: “GET /wp-admin/ HTTP/2.0”, upstream: “fastcgi://unix:/var/lib/php5-fpm/web9_4bcbe6a1.sock:”, host: “[DOMAIN…]”, referrer: “[DOMAIN…]/wp-login”
Downgrading the plugin again to the previous version 3.7.4 fixed this issue. Please consider looking into this issue as a global bug implemented in v3.8.0 of your plugin. I’m looking forward to v3.8.1 including a fix for this, so we can reactivate automatical plugin updates once again for your plugin.
Best regards!
Jennifer Bezkorov
creationell Werbeagentur
Hi @creationell
I understand that the issue may appear to be the same and it may seem like it’s a bug.
However, as per this forum’s guidelines, please start a separate topic of your own and we’ll assist you there.
https://wordpress.org/support/forum-user-guide/faq/#i-have-the-same-problem-can-i-just-reply-to-someone-elses-post-with-me-too
Kind regards,
Adam
I am having the same issue with all my client sites. Admins can login just fine but editors and authors get the “There was a critical error on your website…” message.
Any help would be greatly appreciated.
Hi There
An update in this case, we found the issue and this is happening for non-admin roles when accessing the WordPress dashboard.
A fix is implemented and I hope we can release it soon.
A temporary solution is by using this script:
<?php
add_action('plugins_loaded', function () {
if (!is_admin()) {
return;
}
global $wp_filter;
foreach ($wp_filter['admin_head']->callbacks as $priority => $callbacks) {
foreach ($callbacks as $callback) {
if (is_array($callback['function']) && $callback['function'][1] === 'wphb_style_upgrade_pro_upsell') {
remove_action('admin_head', $callback['function'], $priority);
}
}
}
}, 99999);
As a mu-plugin: https://wpmudev.com/docs/using-wordpress/installing-wordpress-plugins/#installing-mu-plugins
Please keep eyes in the plugin update, after we release the fix you can remove the mu-plugin.
Best Regards
Patrick Freitas
When will you release a fix?
Hi @fuzzybo
The fix was implemented on May 2. Update the plugin and the problem should go away.
Kind Regards,
Kris
Hi there,
Since the fix was already implemented in the plugin and released, I’m marking this as resolved.
If you have any other questions or requite further assistance, please start new topics and we’ll be happy to help there.
Kind regards,
Adam
