Thank you for implementing Feeds SQL, it solved a big issue in my project as I needed to keep in sync Drupal Commerce items quantity with an external POS system.
I run a synchronisation task via cron, and every time I run it I notice the following in the logs:
Notice: Undefined index: FeedsSQLParser in FeedsSource->getConfigFor() (line 577 of //sites/all/modules/feeds/includes/FeedsSource.inc).
Followed by:
Notice: Array to string conversion in FeedsFetcherResult->sanitizeRaw() (line 70 of //sites/all/modules/feeds/plugins/FeedsFetcher.inc).
Does it ring any bell?
The Select query looks fine and I've even tested with myPHPAdmin against the above mentioned POS DB.
Having said, please keep this module alive as it's very useful.
Comments
Comment #1
cdanni commentedI got these same errors when I ran the import manually. It doesn't seem to cause any issues with the import, but it will end up cluttering up the logs eventually. Has a solution been found?
Comment #2
FrancescoUK commentedRe "Notice: Array to string conversion in FeedsFetcherResult->sanitizeRaw() " the solution is here: http://drupal.org/node/1388544
Comment #3
timmay commentedI'm having this problem as well. Feeds importing via SQL from a db was working fine for a few months, and then something changed -- either the source data, or permissions, or domain access, or any combination of those.
On a multi-domain installation, the Feeds Importer setup "preview" shows the data is being queried correctly. It also works correctly queried directly in the database. But when actually running the importer it says it imported 6 records (as opposed to the 600+ it's supposed to), but in reality I'm pretty sure it's not doing anything. Nor will it delete those records.
Running cron gives some indications:
Also:
Tried switching domains, switching admins when running the importer, putting site into maintenance mode, checking permissions, implementing a couple of minor patches, cloning the importers and trying again...nothing changes.
My personal opinion is that there was a bad row in the last import it ran which caused it to choke invisibly, and now it's hung up there and I don't know how to release it. Can I delete the index in the db? How do I go about troubleshooting this problem?
Thanks for any help.
Comment #4
timmay commentedUpdate: I had temporarily fixed this by changing my mappings. Previously I was mapping an external table id to a url for my unique target, but changed it to map to a GUID and it re-imported. But then I deleted the data through the feed importer interface to clean up a few things, and now it doesn't work at all, no matter how I change the mappings, or any other setting.
Cron still says "failed importing 3 nodes".
It's like there a queue somewhere that is messed up that needs to be cleaned out, but I can't find out.
Please, any help? this is a huge deal for our public project.
Comment #5
timmay commentedWhile it's not directly related to the op here,http://drupal.org/node/1673982#comment-6207436 ended up being the resolution to our problem. (confusion with standalone form)
Comment #6
FrancescoUK commentedRe "Notice: Undefined index: FeedsSQLParser in FeedsSource->getConfigFor()" the solution is here: http://drupal.org/node/1271502
Comment #7
FrancescoUK commentedI close this issue as the two points in my original report have been solved elsewhere.
Please read #2 and #6.