"Cannot use object of type stdClass as array" breaking update-core.php

[adamthomsonnz]

I get this error when I go to the update core page:

Fatal error: Uncaught Error: Cannot use object of type stdClass as array in /home/industryawards/public_html/wp-admin/update-core.php:258 Stack trace: #0 /home/industryawards/public_html/wp-admin/update-core.php(625): list_plugin_updates() #1 {main} thrown in /home/industryawards/public_html/wp-admin/update-core.php on line 258


It displays above the plugin list, and no plugins are displayed in the list. The page actually breaks there. I'll attach a screenshot if I can.

However, the error does not happen on the 'Update Available' plugin page tab which can still be used to update plugins. industryawards.co.nz/wp-admin/plugins.php?plugin_status=upgrade

The plugins installed and activated are:

BackupBuddy – 8.2.8.1
Beaver Builder Plugin (Pro Version) – 2.1.3.5
Beaver Themer – 1.1.2.1
PowerPack for Beaver Builder – 2.6.6.1
Better Search Replace – 1.3.2
Blackhole for Bad Bots – 1.9.2
Breadcrumb NavXT – 6.1.0
Duplicate Page – 2.6
Easy Theme and Plugin Upgrades – 2.0.0
Google Analytics Dashboard for WP (GADWP) – 5.3.5
GP Conditional Pricing – 1.2.36
Gravity Perks – 2.0.9
Gravity Forms – 2.3.3
GravityView – 2.0.14
Invisible reCaptcha – 1.2.1
Lazy Load for Videos – 2.4.0
Recent Posts Widget With Thumbnails – 6.2
WC Custom Add to Cart labels – 1.1
WooCommerce Stripe Gateway – 4.1.8
WooCommerce - Gravity Forms Product Add-Ons – 3.3.3
WooCommerce PDF Invoices – 4.1.9
WooCommerce – 3.4.3
Wordfence Security – 7.1.9
WordPress Importer – 0.6.4
Yoast SEO Premium – 5.8

Everything is at it's latest version with the exception of GravityView, but I've eliminated that as a suspect by disabling it.

[SergeyBiryukov]

Hi @adamthomsonnz, welcome to WordPress Trac! Thanks for the report.

It looks like some plugin is filtering the updates list, breaking it. Does the issue still happen with all plugins disabled and a default theme (Twenty Seventeen) activated?

Related: #34052

[karmatosed]

Thank you for reporting this issue. Quite some time has passed, and as no feedback has been given, my recommendation is to move this to close and do just that until we get more information. If more details become available, we can certainly continue exploring. Until then, I think closing with an invalid makes sense. However, we can as I mentioned always reopen.