[wp-trac] [WordPress Trac] #33330: Undefined property: stdClass::$slug

[WordPress Trac]

#33330: Undefined property: stdClass::$slug
--------------------------+-----------------------
 Reporter:  mattfiocca    |       Owner:
     Type:  defect (bug)  |      Status:  reopened
 Priority:  normal        |   Milestone:
Component:  Plugins       |     Version:
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+-----------------------
Changes (by kraftbj):

 * keywords:   => has-patch
 * status:  closed => reopened
 * version:  4.2.4 =>
 * resolution:  invalid =>


Comment:

 Replying to [comment:6 dd32]:
 > FYI; This is most likely caused by a broken 3rd-party plugin updater
 (Usually Paid-for plugins).

 An example is the WooThemes Updater plugin. Example output from the
 site_transient `update_plugins` showing an expected and unexpected result:

 {{{
 ["yourls-wordpress-to-twitter/plugin.php"]=>
     object(stdClass)#838 (6) {
       ["id"]=>
       string(4) "8029"
       ["slug"]=>
       string(27) "yourls-wordpress-to-twitter"
       ["plugin"]=>
       string(38) "yourls-wordpress-to-twitter/plugin.php"
       ["new_version"]=>
       string(5) "1.6.1"
       ["url"]=>
       string(58) "https://wordpress.org/plugins/yourls-wordpress-to-
 twitter/"
       ["package"]=>
       string(76) "https://downloads.wordpress.org/plugin/yourls-wordpress-
 to-twitter.1.6.1.zip"
     }
     ["woothemes-updater/woothemes-updater.php"]=>
     object(stdClass)#839 (1) {
       ["no_update"]=>
       string(30) "Already on the latest version."
     }
 }}}

 We can compensate for it by ensuring the `$plugin->slug` is set to save
 all of those bits and bytes recorded in logs everywhere. Patch incoming.

 I reported it to the folks on the Woo side as well.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/33330#comment:9>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform