Opportunity attachments and mime types

[rocketraman]

It seems that download.php sends attachments to the browser as content-type application/force-download. Is there any reason that download.php does not set the content type to the mime type stored in the notes table?

e.g.

 header("Content-type: " . $row['file_mime_type']); 
  

[wjohnson]

I'm having the same problem. I'm hoping it is a problem with the files being opened and not the files being saved. I just took a look at my cache/upload directory and before I upgraded from 4.2.1 to 4.5.0e the pdf documents had extensions in the directory while other files did not. Now no files have an extension on the end of them. When I try to save the file instead of picking a program to open the file it does not have an extension on the end of it.

I saw in another directory that attachments are getting corrupted when saved. I hope this is not the case for me. I'm going to do a bit more research on this.

[wjohnson]

After a little bit of research it appears as if after upgrading from 4.2.1 to 4.5.0e that the extension on attachments that have been archived or attached as a history item will not open but do not seem to be corrupted. The attachments do not have a file extension when being opened yet have a file extension listed in the filename within sugar. I do not know if the problem is with the attachments being saved or if it is a problem with attachments being read.

Right now every time somebody wants to open an attachment that was saved since the upgrade they have to manually select the program to open the file. They can't use the "always use this program to open this file type" option because the files being sent to the browser have no extension.

I am waiting for a support case to be fixed before upgrading to 4.5.0f. Maybe that will solve this problem but I didn't notice the problem being listed as fixed in those release notes.

Anybody else experiencing this?

[wjohnson]

I don't know why I didn't search bugs first:
http://www.sugarcrm.com/crm/?option=...c-453f860d6b69

Would it be possible to get a hotfix for this if it is going to be a few days before 4.5.0g is released which this is supposed to be fixed in?