Actually if the path to the file that's going to be imported, is not pointing to any file, this message is used:
"The selected file could not be saved. The file is not a known image format."

For better troubleshooting i think, the message should sound more like this one:
"The selected file could not be found."

CommentFileSizeAuthor
#3 filefield.migrate.inc_message.patch2.41 KBwapnik

Comments

wapnik’s picture

Project: Migrate Extras » FileField
Version: 6.x-1.x-dev » 6.x-3.x-dev
Component: Filefield » Code

I see now this is more an issue for filefield and its field_file_save_file function.

quicksketch’s picture

Project: FileField » Migrate Extras
Version: 6.x-3.x-dev » 6.x-1.x-dev
Component: Code » Filefield

This message is typically only shown when a user tries to upload a file that is not a valid image, such as if they upload a BMP file or something. The message is accurate in the usual situations where you would encounter it. The message that the file doesn't exist would be extremely rare in a situation where a user is uploading a new file (since it obviously exists if they just uploaded it).

I'd probably suggest that Migrate Extras check that the file exists before trying to save it (however it does that).

wapnik’s picture

Status: Active » Needs review
StatusFileSize
new2.41 KB

Yes sounds logical.

However Migrate Extras does not check if the file exists, it relies on the field_file_save_file function to do the validations. So here is a patch with my implementation.

wapnik’s picture

#825352 duplicate
suckafucka so i was wasting my time
whose message is prettier? :)

mikeryan’s picture