Skip to content
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

Check if Installed Plugins Are No Longer in the Plugin Directory #36

Open
miya0001 opened this Issue Feb 17, 2017 · 8 comments

Comments

7 participants
@miya0001
Copy link
Member

commented Feb 17, 2017

https://wptavern.com/how-to-check-if-installed-plugins-are-no-longer-in-the-plugin-directory

Displays whether it is in plugin directory like following.

$ wp plugin list
+-----------------------+--------+--------+---------+-----------------+
| name                  | status | update | version | wordpress.org   |
+-----------------------+--------+--------+---------+-----------------+
| hello-dolly           | active | none   | 1.6     | true            |
| jetpack               | active | none   | 4.6     | true            |
| my-plugin             | active | none   | 0.1.0   | false           |
+-----------------------+--------+--------+---------+-----------------+
@1naveengiri

This comment has been minimized.

Copy link

commented Apr 22, 2017

can you suggest in points? how it will be helpful.

@swissspidy

This comment has been minimized.

Copy link
Member

commented Jun 28, 2017

I recently created this as a composer drop-in: https://github.com/wearerequired/composer-scripts

It's useful when you want to quickly list abandoned plugins that you should probably replace.

@danielbachhuber

This comment has been minimized.

Copy link
Member

commented Jun 28, 2017

@swissspidy It looks like your implementation simply compares the last_updated value from the plugins API. If this is the case, the WP-CLI implementation could add an optional last_updated column to wp plugin list with some human-readable value.

@swissspidy

This comment has been minimized.

Copy link
Member

commented Jun 28, 2017

Yep, could be as simple as that.

@eriktorsner

This comment has been minimized.

Copy link

commented Aug 29, 2017

Couldn't tell from reading the code, but does it detect plugins that are removed from the wordpress.org repo?

@swissspidy

This comment has been minimized.

Copy link
Member

commented May 2, 2018

Yes, that composer drop-in detects if a plugin:

  • has been pulled from the WordPress Plugin Directory (usually still available via Subversion).
  • has not been updated in over two years and thus should be used carefully.
@marksabbath

This comment has been minimized.

Copy link

commented Jul 20, 2018

Working on this one.

@marksabbath

This comment has been minimized.

Copy link

commented Jul 20, 2018

I've implemented this here and since it needs to contact the wp repository, wp plugin list is considerably slowed.

At this point, I'm not sure if this is something that would fit in the wp plugin list itself.

Could someone review the code and let me know if there's anything we could do to make it better?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.