Lots of notices on Plugin Report page

[jphorn]

Hi,

I'm seeing lots of notices for Undefined property: stdClass::<variable> on the Plugin Report admin page in our staging environment.

Notice: Undefined property: stdClass::$version in /home/example/www/wp-content/plugins/plugin-report/rt-plugin-report.php on line 370

Notice: Undefined property: stdClass::$version in /home/example/www/wp-content/plugins/plugin-report/rt-plugin-report.php on line 373

Notice: Undefined property: stdClass::$version in /home/example/www/wp-content/plugins/plugin-report/rt-plugin-report.php on line 390

Notice: Undefined property: stdClass::$tested in /home/example/www/wp-content/plugins/plugin-report/rt-plugin-report.php on line 408

Notice: Undefined property: stdClass::$tested in /home/example/www/wp-content/plugins/plugin-report/rt-plugin-report.php on line 409

Notice: Undefined property: stdClass::$num_ratings in /home/example/www/wp-content/plugins/plugin-report/rt-plugin-report.php on line 415

Notice: Undefined property: stdClass::$num_ratings in /home/example/www/wp-content/plugins/plugin-report/rt-plugin-report.php on line 416

Currently running WordPress version 5.3.2 and PHP version 7.2.27.

[roytanck]

Thanks for reporting this. I'll look into it.

[roytanck]

I'm unable to reproduce this issue. It would appear that the wordpress.org plugins API is unreachable or returning incomplete data. Another option could be that some other plugin is filtering the results before they get to our code.

Let's keep this issue open and see if it pops up anywhere else. In which case we can investigate.

[apermo]

This was caused by the wordpress.org API returning an incomplete repo_info object (with missing properties like version, tested, num_ratings). The 2020 code (v1.7) only checked isset( $report['repo_info'] ) before accessing those properties, so PHP threw notices when they were absent.

The current develop branch (2.2.2) already guards tested, num_ratings, rating, and last_updated with individual isset() checks. The one remaining gap — ->version — is fixed by #92.

Summary: all notices from this issue are fixed in the current codebase. Once #92 is merged, the last unguarded property access (->version) is covered too. This can be closed.