[wp-trac] [WordPress Trac] #27722: Don't fire a warning when the WP API timeouts — or do so properly.

[WordPress Trac]

#27722: Don't fire a warning when the WP API timeouts — or do so properly.
-------------------------------+--------------------------
 Reporter:  Denis-de-Bernardy  |       Owner:  johnbillion
     Type:  defect (bug)       |      Status:  accepted
 Priority:  normal             |   Milestone:  4.4
Component:  Upgrade/Install    |     Version:  3.7.1
 Severity:  normal             |  Resolution:
 Keywords:  needs-patch        |     Focuses:
-------------------------------+--------------------------

Comment (by NickDuncan):

 This could also be triggered as a result of plugins making use of the
 "plugins_api" filter to modify where their plugins' are updated from. i.e.
 doing a wp_remote_post to their own server instead of WordPress.org and
 the result being a timed out connection or an unknown response, thereby
 resulting in the error being thrown.

 I suppose we need to understand why the error is being shown in the first
 place and if it is in fact helpful.

 I believe our options are as follows:
 1. Simply do not show the error
 2. Show the error, but give more detail so they user can make an informed
 decision
 3. Show the error with more detail but perhaps show it in the normal <div
 class='error'> notice instead of the traditional WP_Error output.

 Can we get a consensus on what we all feel is the best option? I can then
 try come up with a patch.

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