I have tried to import classifieds from outside sources into my Drupal site via RSS, using Feed API. It seems to work great, with all the ads coming in as they should. But it only lasts five minutes until cron runs, and then the ads disappear. I've tried different Feed API configurations, but still the same result.

I'm assuming this has something to do with the ad expiration feature in the module. Not sure if anyone has any advice on how I could make this work, but would appreciate any suggestions. Thanks.

Comments

fgm’s picture

Status: Active » Postponed (maintainer needs more info)

Can you explain what you mean by "disappear" ? Are the nodes unpublished (because they expire, probably ?) or completely deleted ?

It could also be related to your Feeds configuration, which might delete its own creations when they are replaced by newer ones.

kirkcaraway’s picture

The nodes would unpublish. It's been a while since I tried this. I found a workaround by creating a different content type and using Views to sort these to the bottom, below user-submitted ads. I also had Feeds expire old ads after X number of days. It works, but not ideal. Thanks.

fgm’s picture

Version: 6.x-2.0-alpha6 » 6.x-3.x-dev

If they are unpublished on cron, it likely means that this is related to the expiration date on the nodes, as you suggested. The likely culprit is the fact that, at least in 6.x-2.x and earlier versions, some recomputing is done in FAPI-dependent code, which is not triggered when doing a plain node_save(), as Feeds likely does, meaning that you probably need to massage your imported nodes a bit more to prepare the nodes so that they have all the extra data that the module would normally inject from FAPI.

This is supposed no longer to happen with 6.x-3.x, where node_save() triggers the full node preparation, and the FAPI validation handler passes the node to node_save essentially like you get it from a node_load, just with modified values.

You could try using 6.x-3.x or 6.x-3.0-beta2 to see if the problem is fixed there, because this is inherent to Classified 2 and is unlikely to be fixed on that obsolete branch.

kirkcaraway’s picture

Thanks. I will give 6.x-3 a try and see if it corrects the problem.

fgm’s picture

Any news, four months later ?

fgm’s picture

Status: Postponed (maintainer needs more info) » Fixed

No answer in almost one year, assuming fixed. Feel free to reopen if you have more info.

Status: Fixed » Closed (fixed)

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