Yahnis Elsts

Here are some ideas: - Does this _only_ happen if you add a custom namespace to the update checker? - Is the plugin file name correct? Ideally, it should be...

> I'm not entirely sure if that is what you are asking, but the plugin is in wp-content/plugins/my-plugin/my-plugin.php and I pass 'my-plugin' to buildUpdateChecker Do you mean that you literally...

That doesn't seem like the best idea. It looks like it combines the screenshots from the currently installed version with screenshot descriptions from the latest version. There's no guarantee that...

Currently, that is not possible. The update checker doesn't have any support for partial updates. Also, this update checker doesn't actually *install* updates - it lets WordPress core do that....

I think this issue should be fixed in version 4.8. Unfortunately, there's no way to retroactively fix a conflict between two plugins that are both using older versions of the...

Unfortunately, I have no personal experience with WP Engine or their plugin updater. That said, this library works fine with some other third-party updaters like WP-CLI and (probably) ManageWP, so...

While the ZIP folder structure that you've posted looks correct, my guess would _still_ be that the problem has to do with the folder structure. There are two main possibilities:...

The update checker class has a few subclasses and only those that are related to VCS (e.g. GitHub) have a `setAuthentication` method. My guess would be that you've somehow received...

That code looks fine to me. Here are a few ideas: - Make sure that all PUC files are present and valid (i.e. not zero bytes in size or otherwise...

Admin Menu Editor Pro uses the PUC JSON update format instead of the GitLab/GitHub API. Maybe that's why it isn't be affected by this particular error. I would still recommend...