By cirotix on

I am running Drupal 4.7rc1 and am using aggregator2. Everything seems to work well but when I want to edit one of the node that have been created by aggregator2, to promote it on the front page for exemple, it returns me the following errors:

Invalid feed selected

However I am sure that the correct feed is selected (and actually I try with all the feed that where available in the feed selector).

Is it a known problem (or shouldn't I use the cvs version of the module with drupal 4.7)?

⋅ Categories: Drupal 4.7.x

Comments

hadishon’s picture

hadishon commented

I haven't been able to get Aggregator2.module to work right on drupal 4.7 rc1 yet myself...

2 of my Drupal sites:
Small Farm Resource Center
Israel Travel Center

cirotix’s picture

cirotix commented

The fact is that in the form the if of the feed (fid) is changed with the name of the feed.

The drop-down list which should propose you the name of the feed is displaying the number of the field instead. So when it should send the number of the field it receive its name instead. Hence the error.

I will try to fix that and submit a patch

Edit: the solution is to change line 761
from
$feeds[$temp['title']] = $temp['nid'];
to
$feeds[$temp['nid']] = $temp['title'];

tvbarn’s picture

tvbarn commented

While it's true that patch replaces the bewildering node ID with the more sensible title, it does NOT eliminate the 'Invalid feed selected' problem.

Why the heck is it even checking my feed? The dropdown menu only lists valid feeds. Right?

cirotix’s picture

cirotix commented

While it's true that patch replaces the bewildering node ID with the more sensible title, it does NOT eliminate the 'Invalid feed selected' problem.

As the title says, the patch solves the problem for me.

Why the heck is it even checking my feed? The dropdown menu only lists valid feeds. Right?

Still it needs to know to which feed the item belongs to. Probably a dropdown list is not necessary has the feed from which comes the feed item is already known.