Each time cron is run and the feeds are pulled in again, new nodes are created even if they had been previously created on an earlier cron run. This leads to lots of duplicate nodes being created within the site.

Comments

akalsey’s picture

akalsey commented
Status: Active » Postponed (maintainer needs more info)

What are the feed urls you're pulling in?

samc’s picture

samc commented

I've just been wrangling with the same problem. In my case it turned out that the schema updates had failed to apply. In particular, update_2 which adds the 'changed' column wasn't ever applied in spite of running update.php. This may be because I installed stable then dev without uninstalling first.

After manually applying the updates (via the dropdown in update.php), the issue is resolved.

akalsey’s picture

akalsey commented
Status: Postponed (maintainer needs more info) » Fixed

I've added a check that the item was added to the activitystream table properly before a node gets created. Now if the DB query fails for any reason, a node won't be created.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.

akalsey’s picture

akalsey commented
Status: Closed (fixed) » Fixed

Undoing status change made by bot. Leaving as "fixed" until this goes into a release.

Anonymous’s picture

Anonymous (not verified) commented
Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.