EDIT: Are you using the standard field name, photo? You need to stick to that name and core field, otherwise it won’t work. If you want to use a custom field you would have to add your own custom code to handle it.
Either change to use the default field (I recommend this) or stick to your field and add an after_save logic hook that replicates the code in that PR to copy the photo file.
I know that it’s an old topic, but I still got this issue.
Got the exact same name of Image field in lead and account : rib_c
After conversion, the file isn’t here, in fact in the upload folder I can see the file with the OLD id of the fresh converted lead. So this ID isn’t in the database anymore cause the lead have been converted.
If I rename the file with the new account created, everything work fine. So we just need to rename the file with the new ID. Its on my todo list, I think I can do this in view.convertlead.php or a file like that.
And I have like @nwt, the name of the file in the editview, if I download it I got the “No-Image.png”, cause he cant find any image related.
So what would be desired generic behaviour? During conversion, check each and every field to see if it is “picture” type (or whatever that is called, I didn’t check), and copy the file if it is?
what if somebody doesn’t want some fields copied? What is desirable for one person’s conversion, might not be desirable for the other…
And I wonder if from modules/Leads/views/view.convertlead.php there is any quick, practical way to get the field type… I can’t check now, haven’t looked at this code for years…
For me, It was generic, like if you have a custom text field in lead with the same name in account, it will copy it automatically, so if you have an image field with the same name in both lead and account it should do it too…
I mean if it do this with text field why not image field too ahah.