Hi All,

Is anyone else having trouble with links to files from the Overview / Dashboard pages?

They work fine when viewing the Files tab or a message to which files are attached, but otherwise I get a “page not found” error when basecamp tries to link to the files area

Regards,
David

They’re broken for me too. The initial redirect seems to work (e.g. https://company.projectpath.com/F6734584) but the destination page (e.g. https://company.projectpath.com/projects/1050649/files/download/6734584) results in an error.

Working as advertised for me.

Working for me and I must say slipping in this new ability (to download files directly from the overview page) is most welcome.

Thank you Jason + crew!

They are indeed broken. I believe it probably has to do with whether or not you use your personal storage or BC storage. It’s broken when using your own storage.

We’re aware of this and looking into it right now. We apologize for the inconvenience. It appears to be isolated to people using their own FTP servers. We’re on it.

I’m having the same problem, please advise.

jojo

The problem has been fixed now. We apologize for the inconvenience. Thanks for your patience.

Thanks for the fix. On a semi-related note I uploaded a file with the .jpeg extension a moment ago and the relevant file format thumbnail appears to be missing. The image BC tries to display is https://asset0.projectpath.com/images/icon_JPEG_big.gif, which doesn’t exist.

We used to be able to right click on a file, select save link as and the file would be saved. Now when we do it, we get a number (as described by Dom above) rather than the file name come up and the wrong file extension (e.g. a Word doc will save as an Excel file!).

Rich/Dom, right-click the file name, not the icon. You are right clicking the icon and that’s saving the actual icon image.

Jason,

Definitely clicking the file name.

Odd, it’s working just fine for us in every browser we support. Right clicking the file name on the Dashboard or Overview screen, and copying the link, gives us a link directly to the file. We’ll dig deeper, but if we can’t replicate it’s tough to track down.

Tried it in IE 7 and Safari 3 as well as FF. This is what it looks like when I try to ‘Save Link AS’ for a PDF called – Transfer Analysis:

http://richallum.backpackit.com/assets/1120/106/Files.bmp

By the way, how do I embed an image here?

Anyone else having this problem? When we want to download files from a project (ofetn 20+) we now have to ooen each one and then save it rather than just right clicking and selecting save.

I’m on a PC with personal rather than Basecamp storage.

In Firefox the Save Link is trying to save a HTML file (e.g. F6842346.htm) from the Dashboard, project Overview and the Files pages, instead of the actual file.

If you follow the link rather than trying to save the target then the file will download – I guess that URLs like http://company.projectpath.com/F6842587 redirect to the actual files.

In IE6 it works, and will save the actual file.

Thanks for the response Jason, however you’re misinterpreting my problem. File links are indeed now working perfectly for me, however one of the icons that should appear next to an uploaded file is missing. The mission icon is specific to the .jpeg file extension, whilst the .jpg extension icon appears as it should. It’s only a minor issue but I thought I’d let you know.

Dom:
I see the same image missing (icon_JPEG_big.gif ) – the small icon (icon_JPEG_small.gif) seems to be there though. Did someone delete it? :-)

I have the same problem as johnb two posts up. I’m on Firefox 2 on Mac. When I right-click and hit save, the file downloads—but its filename is something along the lines of “F6825543.htm”. It should have been a jpg.

Checking out the headers… if I had to guess: is it because you’re sending “Content-Type: text/html; charset=utf-8” along with the 302 reply to GET /projects/12345/files/download/6825543? On that response, you send me to s3 with the 302 and a Location header, but you also sent that Content-Type and a Content-Length. That doesn’t sound right. You should just be sending me a 302 and a Location, and you should leave it up to Amazon to give me the content headers.

Problem fixed now from my perspective.

Johnb, thanks for confirming I’m not going mad.

I just ran into the same “icon_JPEG_big.gif” missing. In IE7, it’s no too bad (just one of those squares with a red X in it. But in Firefox 2.0 the text “icon_JPEG_big” appears and overwrites the actual file name, which is very distracting.

I also have the same problem as Chris Kampmeier above but am on Safari 3.1 on a mac. When I right-click the file and hit “download linked file as”, it just downloads an .htm file. The file is actually an mp3 and the htm file when opened links to a quicktime page that will stream the file but gives no options for saving. I have the same problem in Firefox but at least there when I open the htm file i can save the quicktime stream as an mp3.

I can also get around this problem with firefox by renaming the file with the proper file extension in the “Save File As” dialog, but some of my clients don’t have firefox and use safari exclusively. I have not found any way within Safari to download the actual mp3 file. Is there a different way to post the file that would allow Safari to see the proper extension and save it right? Is this purely an issue with the way Amazon is serving the file?

...adding to rhesje’s post. I was trying to figure out why more users weren’t experiencing the same problem, and I thought it was worth noting that we are using the Basecamp API to post these these MP3 files as attachments to a message. The posts appear to be successful and we have no problem downloading them from IE6, IE7 or Firefox 2 on a PC – the problem only occurs when using Safari or Firefox on a Mac. Our only Mac just went for lunch so I am unable to test this further at present, but I thought I would add this to the discussion in the hope that it can help Jason/37Signals troubleshoot it on their end. When our Mac gets back, we will test downloading a manually posted (as opposed to API posted) MP3 file using Safari to further troubleshoot this issue.

One of the reason’s we went with Basecamp was because we wanted to support our Mac clients, so I hope we are able to resolve this issue.

Chris Kampmeier – were you also trying to download files that were posted via the API? Did you ever find a solution? Could there be a problem with either the API or the code we are using?

I tried posting a short Mp3 file without using the API with the same result. it must have something to do with the way Amazon is linking the file is the only thing I can think of.