Skip to content

Commit 59f6e8a

Browse files
committed
wip
1 parent 269c95a commit 59f6e8a

File tree

1 file changed

+12
-1
lines changed

1 file changed

+12
-1
lines changed

README.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -112,13 +112,24 @@ Moreover, even if a plugin is closed, its existing versions are still downloadab
112112

113113
To catch these closed plugins, `WP Org Closed Plugin` queries [WordPress.org API](https://codex.wordpress.org/WordPress.org_API#Plugins) to check whether a plugin is closed and mark them as abandoned in Composer.
114114

115+
## What to do when a plugin is closed
116+
117+
It depends on the reason [why the plugin is closed](https://developer.wordpress.org/plugins/wordpress-org/alerts-and-warnings/#reasons-why-plugins-are-closed).
118+
119+
For security concerns, you should stop using the plugin immediately.
120+
121+
For [plugin exodus](https://wptavern.com/developers-remove-plugins-from-wordpress-org-repository-after-acf-controversy), you should install the plugin via the new repository suggested by the plugin author.
122+
123+
For other reasons, you should do your own research.
124+
125+
115126
## Caveats
116127

117128
### <q>No longer maintained</q>
118129

119130
Composer hardcodes the message <q>no longer maintained</q> for abandoned packages.
120131

121-
Plugins closed on WordPress.org may be closed for various reasons - some are permanent, some are temporary.
132+
Plugins closed on WordPress.org may be [closed for various reasons](https://developer.wordpress.org/plugins/wordpress-org/alerts-and-warnings/#reasons-why-plugins-are-closed) - some are permanent, some are temporary.
122133
The message <q>no longer maintained</q> may not be accurate in some cases.
123134

124135
You should check the plugin's WordPress.org page for more details.

0 commit comments

Comments
 (0)