[wp-trac] [WordPress Trac] #62132: Make wordpress.org API connections for updates, plugins and themes configurable to a different location

WordPress Trac noreply at wordpress.org
Tue Feb 11 20:41:42 UTC 2025


#62132: Make wordpress.org API connections for updates, plugins and themes
configurable to a different location
-----------------------------+------------------------------
 Reporter:  jamesking56      |       Owner:  (none)
     Type:  feature request  |      Status:  new
 Priority:  normal           |   Milestone:  Awaiting Review
Component:  Upgrade/Install  |     Version:
 Severity:  normal           |  Resolution:
 Keywords:                   |     Focuses:
-----------------------------+------------------------------

Comment (by desmith):

 The most annoying part about the http/https thing, is that it's not
 consistent - some of the existing calls to `api.wordpress.org` use one,
 some use the other. I suppose the URL scheme could be an option added to
 the get_whatever_api_base call, but I'll have to think through the best
 way to do that -- my assumption is that someone doing a "new" API
 implementation today would have it be all-https, because it's not 2006
 anymore, and I'd like it to default to that when appropriate, and avoid
 the extra request when possible.

 I agree that `dotorg` in the name is a terrible idea, but I didn't have a
 better idea myself either :D Things like `PLUGIN_API` felt wrong because
 it's also themes and other stuff; `UPDATE_API` felt wrong because it's
 more than updates. And `WORDPRESS_API` is too vague, could easily be
 misread as something related to an app's own REST stuff.

 Didn't even think about initial installs and env vars, so I'll roll all
 that around in my noodle too.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/62132#comment:14>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list