[wp-meta] [Making WordPress.org] #7057: Make / plugin API for closed plugins that are no longer available

Making WordPress.org noreply at wordpress.org
Wed Nov 29 01:22:45 UTC 2023

#7057: Make / plugin API for closed plugins that are no longer available
 Reporter:  ramon fincken             |       Owner:  (none)
     Type:  enhancement               |      Status:  new
 Priority:  normal                    |   Milestone:
Component:  API                       |  Resolution:
 Keywords:  needs-patch dev-feedback  |

Comment (by dd32):

 Replying to [comment:7 eclev91]:
 > @dd32 What has historically been the process by which that API is
 updated and versioned?

 The version only really changes when the operation of the API changes in a
 significant way, which would be otherwise improperly handled by
 **WordPress core** (Ignoring 3rd-party clients for the most part).

 This probably wouldn't justify a version bump, if it would be an
 additional field being present within the JSON returned.

 > Without more information about how the back end of the plugin repository
 and existing API work, it's hard to propose anything firmer, and nothing
 on which to base a PR.

 The best way forward for this ticket from someone without access to the
 code in question, would be to describe the suggested alteration to the API
 output, for example, something like:

 Currently: { "some-plugin.php": { "error": "Slug not found." } }

 Proposed: `{ "some-plugin.php": { "error": "Unavailable", "code": "closed-
 author-request", "reason": "Closed by author request" } }
 (Those are just examples, not the actual existing API responses)

Ticket URL: <https://meta.trac.wordpress.org/ticket/7057#comment:8>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org

More information about the wp-meta mailing list