[wp-trac] [WordPress Trac] #11585: WordPress should cache failed feed fetches so as to avoid overloading feed sources

WordPress Trac noreply at wordpress.org
Sun Jul 28 22:20:00 UTC 2013


#11585: WordPress should cache failed feed fetches so as to avoid overloading feed
sources
-------------------------------+-----------------------------
 Reporter:  Denis-de-Bernardy  |       Owner:
     Type:  enhancement        |      Status:  new
 Priority:  normal             |   Milestone:  Future Release
Component:  Performance        |     Version:  2.9
 Severity:  normal             |  Resolution:
 Keywords:  has-patch          |
-------------------------------+-----------------------------
Changes (by peterchester):

 * keywords:  needs-patch => has-patch


Comment:

 Ok, I think I have it. But honestly, this part of the code is pretty hard
 to follow. I've tested locally with working and broken feed urls but it
 would be great if this could be tested more thoroughly with feeds that are
 throttled and / or temporarily disabled.

 Some questions that came up in the process:

 * Should we be displaying errors in the RSS widget on the frontend when a
 feed is not working or should we just hide the widget?
 * The error message for a bad feed appears in the RSS admin when you first
 enter it. But after saving it again, the error disappears because the feed
 is cached (empty). Should we be effectively caching the error in the
 widget admin?

--
Ticket URL: <http://core.trac.wordpress.org/ticket/11585#comment:5>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list