Aggregator Feed ID currently unsupported
Martin2010 - February 11, 2009 - 14:56
| Project: | Views |
| Version: | 6.x-2.3 |
| Component: | aggregator data |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
The new version of Views allows us to incorporate Aggregator with it.
Everything works fine so far..but it only let us choose 1 aggregator feed for Views. I need to setup 5 different Aggregator feeds with 5 different Views. And i'd like to do it all with Aggregator.
any ideas ?
Trying to edit the :
Aggregator feed: Feed ID
The unique ID of the aggregator feed.Field, resulted in the following error -
Error: handler for aggregator_feed > fid doesn't exist!
More then one Aggregator feed was available at the time of the error.
#1
depending on your needs, you might look at the Feed API module.
#2
I already did try FeedAPI and hated it. Aggregator is all thats needed.
How soon you think till this Aggregator issue will be fixed ? or Bug fixed.
#3
Since nobody knows the question to that..
can I atleast get support with these 2 :
#1 how to have feeds open in a new window with Views ?
#2 how to have more then one parameter on 1 line using a feed?
For instance I would like to have the Timestamp and Description on the same line... Timestamp followed by Description using Views.
[timestamp] [description]
I tried including the above using "Rewrite the output of this field" option .. but the Timestamp would still appear on a line by itself.
#4
You can get the Timestamp and Description on the same line adding a field Global: Custom text. Insert in text [timestamp] [description]
and Exclude from display timestamp and description fields. Place this fields before in the ordered fields list.
#5
Just noting this down, since I'm running acquia which is a -2.3 version. Feed ID is displayed, bu there isn't a handler defined. Set to fixed if this is fixed in 2.4.
#6
Setting to correct component, sorry.
#7
Hmm. I thought Acquia was running a patched 2.2 version actually.
In any case aggregator_feed.fid has the right handlers now, so I think we can mark this fixed.
#8
Automatically closed -- issue fixed for 2 weeks with no activity.