This is a strange one.
I installed FeedAPI 6.x-1.3 a few days ago. I added several feeds using FeedAPI: Quick create Feed. No problems. The feeds were entered into the 'feedapi' table, the feeds downloaded fine, I was impressed.
I started doing some module development using FeedAPI as a dependency. That was all going well too. I added a bunch of tests feeds, removed them, added them back, etc. Normal dev stuff. Bulletproof.
However, after deleting all the test feeds for the umteenth time, I suddenly found that I couldn't enter a feed anymore. Nothing was getting written to the 'feedapi' table. There were also no error messages.
I figured I must have broken something so I unistalled/removed my module. Still nothing. I uninstalled/removed FeedAPI and its associated dependencies. Still nothing. I downloaded and installed the development API, 6.x-1.3-dev. Then I got an error message:
* Could not retrieve title from feed.
This was from the same RSS feeds I'd successfully added and removed a couple of dozen times before.
I uninstalled 6.x-1.3-dev and downloaded/installed 6.x-1.3 again. Now I get a new error message when I try to add a new Quick Feed:
* warning: Invalid argument supplied for foreach() in /web/htdocs/devel/drupal-6.4/sites/all/modules/feedapi/feedapi.module on line 1279.
* Could not retrieve title from feed.
I uninstalled/removed/reinstalled 6.x-1.3 a couple of more times. No difference. I continue to get those same two error messages.
Beats the heck out of me. The only symptom I noticed is that FeedAPI doesn't clean up all its variables when it's uninstalled. However, I deleted those through Debug, cleaned the cache and reinstalled but it made no difference.
Comments
Comment #1
smanes commentedComment #2
smanes commentedFound the problem.
When I reinstalled I didn't enable a Parser in Content Type -> feed. Enabling one got rid of the problem.
However, it doesn't explain why FeedAPI suddenly failed in the first place today. Could there be some variable corruption? My module doesn't touch FeedAPI's.
Closing this bug for now.