Closed (won't fix)
Project:
FeedAPI
Version:
6.x-1.9-beta3
Component:
Documentation
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
11 Nov 2009 at 19:08 UTC
Updated:
1 Mar 2012 at 05:44 UTC
Jump to comment: Most recent file
Comments
Comment #1
infojunkieSome more information:
The Atom format allows for paged feeds using the syntax
YouTube feeds (e.g. http://gdata.youtube.com/feeds/base/users/GibsonGuitarCorp/uploads) support this feature. In the previous feed, you can find
Comment #2
aron novakTo consume such paginated feeds, you definitely need to write your own parser.
The recipe is easy: handle those 'next' links and download them as well, and process them one-by-one.
Comment #3
infojunkieI went ahead and created a patch for FeedAPI core to handle paginated feeds. The main idea is to refresh one 'next' page whenever the first page remains unchanged. The implementation is as follows:
* Parsers simplepie and common_syndication now return an additional array
$feed->options->pagerconsisting of 'first', 'next', 'previous' and 'last' links.* The 'next' page is stored in field
feedapi.url_nextand is loaded into$feed->url_next.* When function
_feedapi_invoke_refreshfinds that no new items are present, it checks for$feed->url_next. If it's present, it invokes the parser again with this URL. The 'next' page is then updated with the result of this parsing.Thanks for your consideration.
Comment #4
infojunkieSorry, reversed source and destination in the patch. Fixed now.
Comment #5
infojunkieCleaning up my issue queue.