Used a tamper to populate a multi-instance image field without success. After much head banging, I found that the issue was the case of the file extension. The files on the server had uppercase files extensions, and so did my CSV import file names, but for some reason the import couldn't connect the two. I changed the file extensions on the server, and the corresponding names in my CSV file, and the import worked without issue.

You can manually upload an image with an uppercase extension, and it will upload and show up on the server with that uppercase extension and display on the content type page fine, but feeds import/feeds tamper can't handle uppercase file extensions... at least using a tamper with a multi-instance image field.

Comments

hyside created an issue.

saratt’s picture

saratt commented

Hi hyside,

Were you able to figure out how to import the files with uppercase file extension. I am running into the same issue where I am using feeds importer to import images into an image field and the file extension for the image is .JPG and they are not getting imported where as the images with extension .jpg are importing fine.

Thank you.

hyside’s picture

hyside commented

Unfortunately I didn't track this down to patch the issue. In the interest of time I ended up writing a python script to rename all of my image files to use lower-case extensions, and made sure the references to them in the CSV matched, to successfully import that batch, and any subsequent batches.