Skip to content

Commit b4240e4

Browse files
committed
wip
1 parent e73498f commit b4240e4

1 file changed

Lines changed: 15 additions & 15 deletions

File tree

README.md

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -73,10 +73,10 @@ Package wpackagist-plugin/my-closed-plugin is abandoned because https://wordpres
7373

7474
## Why
7575

76-
When a plugin is closed on WordPress.org, [WPackagist](https://wpackagist.org/) not always remove it from its database immediately.
77-
As a result, some closed plugins remain available for installation via WPackagist.
76+
When a plugin is closed on WordPress.org, Composer repositories (e.g: [WPackagist](https://wpackagist.org/) & [WP Packages](https://wp-packages.org/) not always remove it from its database immediately.
77+
Worse still, even after the Composer repositories removed it., a closed plugin might persists in `composer.lock` with references to download.wordPress.org endpoint and [WordPress plugin subversion repository](https://plugins.svn.wordpress.org/)
78+
As a result, closed plugins remain installable.
7879

79-
Moreover, even if a plugin is closed, its existing versions are still downloadable from WordPress.org and the subversion repository.
8080
```json
8181
{
8282
"repositories": [
@@ -87,7 +87,7 @@ Moreover, even if a plugin is closed, its existing versions are still downloadab
8787
"version": "1.0",
8888
"source": {
8989
"type": "svn",
90-
"url": "https://plugins.svn.wordpress.org/my-closed-plugin/",
90+
"url": "https://plugins.svn.wordpress.org/my-closed-plugin/", // subversion repository
9191
"reference": "tags/1.0"
9292
}
9393
}
@@ -99,15 +99,15 @@ Moreover, even if a plugin is closed, its existing versions are still downloadab
9999
"version": "1.0",
100100
"dist": {
101101
"type": "zip",
102-
"url": "https://downloads.wordpress.org/plugin/your-closed-plugin.1.0.zip"
102+
"url": "https://downloads.wordpress.org/plugin/your-closed-plugin.1.0.zip" // download.wordPress.org endpoint
103103
}
104104
}
105105
}
106106
]
107107
}
108108
```
109109

110-
To catch these closed plugins, `WP Org Closed Plugin` queries [wp-packages.org](https://wp-packages.org/) for the list of plugins closed on WordPress.org and marks them as abandoned in Composer.
110+
To catch these closed plugins, `WP Org Closed Plugin` queries [WP Packages API](https://wp-packages.org/api/packages/wp-plugin/closed) for the list of plugins closed on WordPress.org and marks them as abandoned in Composer.
111111

112112
## What to do when a plugin is closed?
113113

@@ -151,15 +151,15 @@ Skipped checking for closed plugins because of --locked.
151151

152152
You should run `composer audit` without `--locked` to check for closed plugins.
153153

154-
### Cache
155-
156-
The list of closed plugins is fetched from [wp-packages.org](https://wp-packages.org/) in a single request and cached for 10 minutes.
157-
158-
If you must clear the cache, delete the `<composer-cache-dir>/wp-org-closed-plugin` directory.
159-
160-
```sh
161-
rm -rf $(composer config cache-dir)/wp-org-closed-plugin
162-
```
154+
> [!TIP]
155+
> **Hire Tang Rufus!**
156+
>
157+
> There is no need to understand any of these quirks.
158+
> Let me handle them for you.
159+
> I am seeking my next job, freelance or full-time.
160+
>
161+
> If you are hiring PHP / Ruby / Go developers,
162+
> contact me at https://typist.tech/contact/
163163
164164
## Installation
165165

0 commit comments

Comments
 (0)