View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005098||Simple:Press||plugins - general||public||2015-09-27 23:57||2017-12-23 16:34|
|Reporter||Mr Papa||Assigned To|
|Priority||normal||Severity||N/A||Reproducibility||have not tried|
|Target Version||Future Release||Fixed in Version|
|Summary||0005098: new plugin: REST endpoint|
|Description||looks like the new REST API for WP is going to hit in 4.4... the feature plugin is currently available... we should think about adding a custom endpoint solution for the REST API...|
this would allow so many things... the REST API is basically a way for an application (could be wp, website or standalone app) to get/add data... so a mobile phone app, for example, could access a wp/sp website to add or display posts... from a wp perspective, it would also allow a wp page to display one forum and another page to display another (folks always want that!)... single forum on page just an example - would be pretty hard to do since you have to do all the display...
since it allows you to get forum data, you can do whatever you want with it.. you could also create new posts via the endpoint.. pretty endless amount of possibilities... so what this does is allow anything that can access a url (ie our endpoint) interact directly with our current API to get/put data...
how hard to do? probably not that hard... its going to mostly be methods for getting or putting data... data is not displayed, just returned... up to the recipient of the data do display how they want... or for the case of putting data, for us to do what we need with the data (ie create post)...
custom endpoint would interact with the WP REST API to define the API methods... the current WP API plugin that is supposed to get pulled into core has pretty good documentation including starter endpoints...
|Tags||No tags attached.|
meant to add, that the hard part here will be figuring out what to support on the endpoint... some obvious examples (these are all fetch):
group view class object
forum view class object (passed in forum id)
topic view class object (passed in topic id)
post object (passed in post id)
all the above would also need a user id so permissions could be checked...
but the list could go on...
list topic class object
list post class object
user profile object
members list class object
etc etc etc
|forget the passing user id... the rest api (wp) will need a way to authenticate (ie login) a user... so should be able to use the current user for checks...|
|2015-09-27 23:57||Mr Papa||New Issue|
|2015-09-27 23:57||Mr Papa||Status||new => assigned|
|2015-09-27 23:57||Mr Papa||Assigned To||=> Mr Papa|
|2015-09-28 00:11||Mr Papa||Note Added: 0016678|
|2015-09-28 00:12||Mr Papa||Change Log Text||=> update|
|2015-09-28 00:12||Mr Papa||Description Updated||View Revisions|
|2015-09-28 01:36||Mr Papa||Description Updated||View Revisions|
|2015-09-28 13:43||Mr Papa||Note Added: 0016679|
|2015-10-18 21:24||Mr Papa||Target Version||5.6 => 5.6.1|
|2015-12-13 21:42||Mr Papa||Target Version||5.6.1 => 5.6.2|
|2016-01-08 01:25||Mr Papa||Target Version||5.6.2 => 5.6.3|
|2016-01-30 01:45||Mr Papa||Target Version||5.6.3 => 5.6.4|
|2016-02-14 21:21||Mr Papa||Target Version||5.6.4 => 5.6.5|
|2016-02-20 07:09||Mr Papa||Target Version||5.6.5 => 5.6.6|
|2016-05-04 16:10||Yellow Swordfish||Target Version||5.6.6 => 5.6.7|
|2016-05-20 21:49||Mr Papa||Target Version||5.6.7 => 5.6.8|
|2016-07-12 00:20||Mr Papa||Target Version||5.6.8 => 5.7|
|2016-07-16 14:48||Mr Papa||Target Version||5.7 => 5.7.1|
|2016-08-20 15:29||Mr Papa||Target Version||5.7.1 => 5.7.2|
|2016-10-05 07:13||Yellow Swordfish||Target Version||5.7.2 => 5.7.3|
|2016-10-08 17:14||Mr Papa||Target Version||5.7.3 => Future Release|
|2017-12-23 16:34||Mr Papa||Assigned To||Mr Papa =>|
|2017-12-23 16:34||Mr Papa||Status||assigned => new|