[wp-trac] [WordPress Trac] #37062: WP Json API

[WordPress Trac]

#37062: WP Json API
--------------------------+-----------------------------
 Reporter:  n-for-all     |      Owner:
     Type:  defect (bug)  |     Status:  new
 Priority:  normal        |  Milestone:  Awaiting Review
Component:  General       |    Version:  4.5
 Severity:  normal        |   Keywords:
  Focuses:                |
--------------------------+-----------------------------
 Why is the API activated by default in v4.4? an extra hole for hacking or
 what? and no option for deactivating?, it should be deactivated by
 default, i am not sure why wordpress dev's always decide what the user
 wants instead of giving him a choice...

 look at xmlrpc i have never used and never plan to use it, and have
 created more than 400 blogs in wordpress and none for the clients asked
 for it, so it is useless activation...

 if your app depends on the xmlrpc or json, it can show a message to
 activate the xmlrpc or json with a link.

 Right now the system start to become very slow, very buggy and the
 database very big for a small amount of posts because of the revisions, a
 site with 5 pages end up with 30 pages in the database, you should split
 the chunks to make sure you save only the modified part of the post, do
 you think a system slow as this can be good for apps developing to
 activate the wp-json be default?

 Is it also worth activating the API because 5% of the blogs might use it?

 We are overloading the system now with security plugins to protect it and
 instead of finding a solution, you add another problem for us to deal with
 "Securing the JSON API"

--
Ticket URL: <https://core.trac.wordpress.org/ticket/37062>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform