[wp-trac] [WordPress Trac] #38731: Allow publicly readable settings within WP_REST_Settings_Controller

WordPress Trac noreply at wordpress.org
Tue Nov 15 02:49:17 UTC 2016


#38731: Allow publicly readable settings within WP_REST_Settings_Controller
-------------------------+------------------------------
 Reporter:  davecpage    |       Owner:
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  REST API     |     Version:  trunk
 Severity:  normal       |  Resolution:
 Keywords:               |     Focuses:
-------------------------+------------------------------

Comment (by jnylen0):

 There was some more discussion on "readonly settings" starting here:
 https://core.trac.wordpress.org/ticket/38490#comment:10

 To summarize, a "readonly setting" is a misnomer because it's not really a
 "setting" as defined by the endpoint that lets you view and edit site
 settings.  This is really "site info".  As such, if it's going to live
 somewhere, it should probably be on the root `/wp-json` endpoint which
 already has some of these properties (site `name`, `description`, `url`,
 and `home`).

 Here's what I think we should do about this (cc @joehoyle @rachelbaker for
 your opinions).

 - Create a new ticket to enhance the `/wp-json` endpoint with any extra
 site properties (the current settings endpoint and the list
 [https://core.trac.wordpress.org/ticket/38490#comment:7 here] are both
 good starting points).  We may also need a mechanism for versioning the
 response of this endpoint and having its response vary based on the user's
 capabilities.  Addressing all of this can wait until a future release.
 - Once we have a plan for adding more site info, close this ticket.

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


More information about the wp-trac mailing list