Support for aggregation in Drupal 5
challer - June 29, 2007 - 15:37
| Project: | GeoRSS module |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | geodaniel |
| Status: | won't fix |
Jump to:
Description
Just wanted to ask what aggregation modules are supported right now? I saw that aggregator2 is now merged into the aggregation module (which I unfortunately can't use, since it's php5 only), and any updates on supporting the leech module? What's the best way to go to aggregate georss feeds at the moment?
Thanks for the info,
Cheers, Chris
#1
Hey Chris...
I'm working on getting the Feedparser support up and running again. It needs work on the GeoRSS module end (which I'm about to commit to CVS) and also on the Feedparser end to get them both working with each other.
I haven't really got anywhere with other aggregation modules, but could try and get it working with them, time permitting. Feedparser is probably the one that will get best support though, followed by SimpleFeed which I see has just been released.
Cheers,
Dan
#2
I've committed the code ready to support Feedparser when it's fully ready for Drupal 5, but right now it doesn't seem to be creating any nodes when it refreshes the feeds and also it doesn't yet have the version of the SimplePie library needed to be able to extract geodata from feeds.
#3
Hi there, I am also trying to use geoRSS + Aggregator + GMap. I have the GeoRSS encoding format set to "Simple" and the Enable extraction of geolocation information from incoming feeds checkbox marked. Allthough, It doesn't seem to be storing coordinates data in any table. Where shoult it be stored? In table "location"? In table "aggregator_feed"?
Is it supposed to work with the plain installation of these modules?
Any suggestions?
Thanks and great work.
#4
Do you mean the core aggregator module? If that's what you mean, it won't work as it doesn't create feed items as nodes. As for other modules to use instead, I haven't done any work with the aggregation side of it recently, so I'm not sure which modules it works with or not right now.
#5
Yes, the core aggregation module(the one that replaced the aggregation2).
Do you mean that geoRSS is not extracting coordinates from rss feeds anymore with this version of the modules?
#6
Does anyone have any combination of Drupal 5.x modules working for GeoRSS/Location/Any Feed Parser. I have tested:
- FeedParser (11/07) without country xx patch and with patch (11/06 version of SimplePie)
- SimpleFeed (has 11/07 version of SimplePie)
- Skipped aggregator, as it does not create nodes.
No luck so far. I had this working a few versions back, but I suspect the multi-location feature may be causing some issues. Any thoughts?
#7
Dan,
My bad for seeming to state the module does not function in my last post. I have used the module and was very happy with the results. Within my current platform (listed below) I have not been as successful. Most likely it has to due with a configuration or customization error on my part. I noticed you changed the status of this thread to 'postponed'. If this means that the 5.x version is postponed, I understand that the rule is either wait or fix it myself and tell you how I did it. I was wondering what 'postponed' means for 5.x GeoRSS module? Do you needs some help?
Drupal 5.x
GeoRSS module 5.x-1.x-dev (2007-Nov-19)
GMap Module 5.x-1.0-alpha1
location (API, module) 5.x-2.7
Feedparser 5.x-1.x-dev (2007-Aug-21)
I selected Feedparser since is seems to fit most of my needs (creates nodes) but has the potential of GeoRSS recognition.
#8
The current suspect for causing lat/lon not being picked up is the version of SimplePie that is used by the FeedParser module. I'm not seeing any get_latitude/get_longitude functions in that version (11/06). I upgraded from simplepie.org website to a later build (11/2/07 Build). Received a blank screen, meaning PHP errors. I now just noticed simplepie 1.1 has been released. I may attempt to get FeedParser working with that version and begin to debug. Another alternative is to used the Feed API or SimpleFeed, which do work with later versions of SimplePie, but will require some work on the GeoRSS module, which seems to require an addition to the case statements throughout the module, by using feedparser as a template and adding simplefeed/feedapi. The downside is that simplefeed still has some bugs that I need to work through and feedapi, although looking like a great design, it is still a bit young.
My options are as follows:
(1) Stay with feedparser and get the right version of SimplePie to work with it. Note that feedparser's 5.x release seems not to be supported (I'm still attempting to understand what this means)
(2) Move to SimpleFeed, work to get the bugs out and modify GeoRSS code.
(3) Move to FeedApi, which does use the current version of SimplePie, and modify GeoRSS code.
(4) Drop GeoRSS, hack the code in FeedApi, adding GeoRSS functionality. They have a module for creating elements that looks very promising, but seems to primarily only work with CCK fields.
One other issue to consider when planning is PHP 5.x. It contains some very fast native parsing capabilities which are exploited by FeedAPI (their native parser, not SimplePie) and possibly the 2.x version of SimplePIe.
Again, I'm just looking for a feed that supports GeoRSS and creates a node for a feed item. Any input would be great.
Must Have: GeoRSS, Feed Item is a Node
Should Haves: support for tags, author, guid ...
Could Have: very scalable design, muti language support
#9
Sorry I've not got back to this issue for quite some time. I've been looking into getting the module to work with the FeedAPI (it's the way forward) this evening but I've not had any luck yet. I haven't as of yet looked back and tried other options.
Ideally we'd be able to drop GeoRSS module altogether and have it all handled by location module (it's already included the improved outgoing GeoRSS support in the latest dev version).
#10
I agree that FeedAPI seems like the best alternative at this time. I had started a thread here http://drupal.org/node/227017 to discuss the issue (FeedAPI feature request). I was also looking at the Feed Element Mapper. At first I discounted it, as being CCK centric, but there is this note on the module page "It also provides a hook based API for mapping any feed item element to any field (=property, in the widest sense of the word) of a node object.".
"Ideally we'd be able to drop GeoRSS module altogether and have it all handled by location module (it's already included the improved outgoing GeoRSS support in the latest dev version)." This sounds promising and thank you for your work. I already use this type of feature on my websites. Very cool. Right now I'm challenged by the incoming GeoRSS support, ergo FeedAPI. I don't see location being the right place for the incoming GeoRss support, due to the complexity and high maintenance of feed parsers. So like you, I was looking at a GeoRSS plug-in leveraging the FeedAPI/Element Mapper as a means for a more robust long terms solution for integration.
#11
The Drupal 5 version of this module is no longer supported.