-
Notifications
You must be signed in to change notification settings - Fork 411
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Easiest way to identify plugins that use plugin-updater-checker #581
Comments
I don't think there's a reliable way to do that. Looking for a specific string like the For plugins that use Composer, you could look for a For active plugins, you could look at callbacks attached to the |
Thanks for your quick response @YahnisElsts It sounds like maybe this would be unreliable and/or require scanning the entire plugin tree, which would probably cause performance issues based on my previous tests doing that. In the future if you end up having a narrower way to check the plugin main files, I'd love to know. Thanks! |
@jessuppi If your goal is to exclude any plugins that aren't from wordpress.org, then see this fragment: #578 (comment) . (The code there isn't restricted to use of any particular updates-checking class). |
Hello, thanks for this awesome project.
I'm currently working on RepoMan which is an MU plugin that extends the native WP plugin search to include plugins from GitHub that can be installed... it also prevents WordPress.org from sending "update" notices on any plugins that RepoMan detects already support the Git Updater software by looking for string
GitHub Plugin URI
in the main file:https://github.com/littlebizzy/repoman
One of your users asked if we could support your software also.
Do you have a recommendation on the easiest way for RepoMan to scan installed plugins in WordPress and identify which plugins support
plugin-update-checker
that is hopefully lightweight and scalable?For example, looking for string
PluginUpdateChecker
in the main file should that be enough? Cheers!The text was updated successfully, but these errors were encountered: