I have a client that wants to manage his parts online. There are 335 parts to upload and I have feeds set up to handle this from a CSV.
I keep getting this error after trying to upload some parts.
cURL error 3: malformed (see http://curl.haxx.se/libcurl/c/libcurl-errors.html)
Sometimes the error will include the information that certain values should not be null, which doesn't make sense because some of the parts will upload.
Any ideas? I have attached the configuration and the screenshot of the error.
Comment | File | Size | Author |
---|---|---|---|
Screen Shot 2018-12-31 at 1.12.53 PM.png | 62.27 KB | Burlyn84 | |
feedconfig.txt | 1.93 KB | Burlyn84 |
Issue fork feeds-3023198
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
Burlyn84 CreditAttribution: Burlyn84 commentedI have figured out something here on this error.
I was calling for photos that didn't exist in the my csv file. I thought the feed would skip over that if there was no such file. But apparently not.
Is that something that could be added to this modules capabilities?
Comment #3
MegaChriz CreditAttribution: MegaChriz at WebCoo commentedI think if a file specified by the source doesn't exist, the item should not be imported. The import is "broken" after all, cause Feeds cannot import everything it is supposed to do. But it would be cool if Feeds would say that it couldn't find the file instead of displaying the curl error.
Comment #4
MegaChriz CreditAttribution: MegaChriz at WebCoo commentedThere are more file target related issues. Tagging this with “Feeds file target”.
Comment #5
gantal CreditAttribution: gantal at Elevated Third commentedTagging for DrupalCamp Colorado's upcoming contrib day.
Comment #7
MegaChriz CreditAttribution: MegaChriz at WebCoo commentedI ran into this issue today, I made the error message slightly more informing. I did notice after trying to import it for a second time, the error was not repeated. This could be because I was still working on the error message at the time, but I think it would not be great if on subsequent imports the missing file is just ignored.