Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #16778, comment 68


Ignore:
Timestamp:
12/07/2016 04:59:29 PM (8 years ago)
Author:
DvanKooten
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #16778, comment 68

    initial v1  
    22> If you wish to filter the data for privacy purposes, then you can do so and it will not affect the update process for small WordPress installations. At present, there is not a secondary update path for large installations, but that does not preclude the possibility of one occurring in the future.
    33
    4 Let me just add here that the proposed filter here does not seem to be entirely sufficient, as the `pre_http_request` filter has to fire off a request off its own, meaning a request can only be pre-fired (or pre-emptied) once. So if two plugins are short-circuiting the request like this, a request is effectively fired twice and the entire point is defeated.
     4Let me just add here that the `pre_http_request` filter here does not seem to be entirely sufficient, as any code hooking into it has to fire off a request off its own, meaning a request can only be pre-fired (or pre-emptied) once. So if two plugins are short-circuiting the request like this, a request is effectively fired twice and the entire point is defeated.
    55
    66This would be _much_ simpler if request URL's could be filtered.