Yahnis Elsts

This does not look like a GitHub problem. Based on the error message that you [posted](https://github.com/YahnisElsts/plugin-update-checker/issues/484#issuecomment-1058011945) earlier, the problem might be something on your WordPress site, such as incorrect file...

Unfortunately, that's currently not possible. Icons and banners are only available when using JSON metadata.

@paulmiller3000 The `Puc_v4p8_Plugin_Info` class also has a `banners` property. It should be an associative array with up to two entries: 1. `low`: URL of a 772x250 banner image. 2. `high`:...

I haven't measured the performance impact of running PUC in the front end, but I expect it to be relatively small. When not actively checking for updates, all it does...

Are you sure that it's actually *checking for updates* every time it shows an update? Normally, it should cache the update information and show that cached update instead of checking...

> [...] if I change the version number of the installed plugin to a version less than the most resent and visit the site the admin bar updates to show...

It will also check more frequently on certain admin pages, like "Dashboard -> Updates". This mimics how WordPress itself checks for updates. Could this explain why you're seeing more frequent...

Yes, that should work. The 4th argument (i.e. the one after the slug) sets the check interval in hours. Setting it to 0 should disable the default cron job and...

I tried to reproduce the issue by using versions 4.4 and 4.7 of the updater on the same site, but I didn't get get the fatal error that you got....

It took me a while to reproduce the issue and figure out what's causing the error. It has to do with how Composer generates autoloaders for packages that use the...