I've just set up a new test site to see if FeedAPI can meet my needs. A clean install of Drupal 5.9 plus the FeedADI 5.x.1.2 module set. Installed on Mac OS X 10.4.11 with MAMP (MySQL 5.0.41 and PHP 5.2.3).

The Drupal install goes fine. I install FeedAPI and activate the modules, and on submitting the form (example.com/admin/build/modules) I get a blank page (example.com/admin/build/modules/confirm). With the FeedAPI modules deactivated when I submit the form I get example.com/admin/build/modules/confirm which changes to example.com/admin/build/modules and then presents the page with the confirmation message.

It may be only a very minor thing, but certainly does not instill any confidence in this user that the module is going to be useable.

Comments

tobedeleted’s picture

tobedeleted commented

That URL should read example.com/admin/build/modules/list/confirm

Further update: using the dev version of the FeedAPI module instead of the official 5.x.1.2 release addresses this problem, but still breaks example.com/admin (i.e. after installing FeedAPI in Drupal 5.9 navigating to /admin presents a blank page.

More tinkering with the various options here gives me a working result if I disable the Simplepie parser (I'm using version 1.1.1 of Simplepie) and use the common syndication parser instead. Seems to be a compatibility issue between D5.9 and the Simplepie module.

aron novak’s picture

aron novak
Primary language Hungarian
Location Hungary, Budapest
commented
Status: Active » Postponed (maintainer needs more info)

Could you look up error log? It was a critical php error, but apache didn't display this. It'd be interesting what happened.

Bevan’s picture

Bevan commented

I always get the following error in FF3 when updating Feed nodes or other actions that result in the feed being aggregated. The data still gets aggregated though

Network Error (tcp_error)

A communication error occurred: ""
The Web Server may be down, too busy, or experiencing other problems preventing it from responding to requests. You may wish to try again at a later time.

For assistance, contact your network support team.

There are no errors in watchdog, except "Cron has been running for more than an hour and is most ..."
The error log was empty suggesting that it hasn't been configured correctly.