I'm running FeedAPI along with FeedAPI Node (5.x-1.x-dev). I created all my feeds just fine and when I hit the refresh button, they refresh just fine. However, they're not refreshing on their own. Am I missing a setting somewhere?

The only bug issue I can think of is that I had previously installed and removed 5.x-1.0-beta6. Even after deleting feedapi related system tables, I'm still showing version 5.x-1.0-beta6 for the FeedMapper (again, even though I removed it and manualy deleted the system table).

Little help here?

(attaching a screenshot of my module list)

CommentFileSizeAuthor
feedapi_settings.png104.49 KBRob_Feature

Comments

Rob_Feature’s picture

Rob_Feature commented
Category: support » bug

Ok, so after a little handwringing, it seems that FeedAPI feeds don't actually update on a Poormanscron cron run. I'm going to mark this as a bug (feel free to change it to something else if deemed necessary) since alot of people are probably using poormanscron with this module and they don't seem to work together.

I'm currently setting up a 'real' cron and will report back if this fixes my refresh issue.

aron novak’s picture

aron novak
Primary language Hungarian
Location Hungary, Budapest
commented
Status: Active » Closed (duplicate)

I cannot do anything. I haven't got any response from poormanscron developers via the issue queue. I'll add the fact of incompatibility to the release notes of FeedAPI.

mfer’s picture

mfer commented
Status: Closed (duplicate) » Postponed (maintainer needs more info)

I'm wondering if the issue is with poormanscron. According to logging poormanscron is executing feedapi_cron.

mfer’s picture

mfer commented

I haven't tested this but, my theory is that since poormanscron is firing at the end of a page load there isn't enough time left (according to feedapi_cron_time()) for feedapi to do it's thing. This would need to be tested and this is just a theory.

aron novak’s picture

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

mfer:
It's not about the execution time. I exactly located the problem.
Have you read my addition to the release notes? Have you realized that poormanscron lacks of handling cron_semaphore?

All in all, it's really a duplicate. If you really have some perfect idea to get feedapi and poormanscron work together, please write to this ticket: http://drupal.org/node/255852 . It's the same topic.