[wp-trac] [WordPress Trac] #48885: REST API: Add a route to read and update separate site settings

[WordPress Trac]

#48885: REST API: Add a route to read and update separate site settings
-------------------------------------------------+-------------------------
 Reporter:  scruffian                            |       Owner:
                                                 |  spacedmonkey
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  5.6
Component:  REST API                             |     Version:
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch has-unit-tests 2nd-        |     Focuses:
  opinion                                        |
-------------------------------------------------+-------------------------

Comment (by spacedmonkey):

 > Something to keep in mind with permission callbacks is that reading
 permission would be different than writing permission. And do we want to
 support a custom write permission callback? And if we do, do we need to
 update options.php to use that capability instead of manage_options.

 As discussed in office hours, I do not believe we should make permission
 callbacks apply to other parts of core like options.php. Read and edit
 callbacks, should be limited to the REST API. The name of the ticket and
 original purpose are clear. To make values from wp_options available to
 read and update via the REST API. To add a whole permission model to
 `register_settings`, is massively out of scope for this ticket and
 introduces edge cases issues we simple do not need to tackle to complete
 this ticket's goal.

 I would love @johnjamesjacoby thoughts on the matter, as he is the
 maintainer of options and meta.

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