A forum for technical support discussion related to Fogbugz.
We just upgraded to 6.0 yesterday.. love the changes.. few tweaks need to be made.. what's up with that huge #ss case number??? You could fit 5 more fields there :-)
Anyhow, after upgrading, we can no longer view attachments (new or old) that are images (gif, jpg, png etc.). We simply get the X. All other attachments seem to be fine.
Any suggestions or anyone else having this issue?
Right click the attachment and open in a new window to see what error message FogBugz is actually dealing with... (it will show up in your browser).
Michael H. Pryor
Wednesday, September 12, 2007
No error message was created.. however I did find something interesting. The images that no longer display all have (had) extensions that were capitalized (i.e. JPG, GIF) instead of the normal lower case. I pulled some of the images and saved them with lowercase extensions, and they now work fine. I'm currently in the process to find out where these files originated (who, when, what application was used to create them etc.)
Do cap extensions need to be included in any of FB's config files to be recongnized?
Nope, we have no restrictions on capitalization... What OS is your fogbugz server and what db are you using?
Also, when you are looking at a case with a big x image in it, and you right click on the image and say "open in a new window" what do you see? Do you see a blank window?
The server is Windows 2003 Standard SP2. Dell PE2850, 4GB RAM, CPU 3.00GHz.
The DB is SQL 2005 9.00.2047.00
It opens a new window with another "X", now error messages.
I can send you a copy of a sample image I had issues with if you'd like.
I installed FB locally on my Laptop to see if it was related to the server environment, I ran into the same problem. My laptop is XP SP2, 4GB RAM, running SQL 2005 9.00.1406.00.
Yes, let's continue this via email as we may need a Fog Creek Copilot session to figure it out.
Did you see ben's question about case sensitive db server?
The DB is no set to be case sensitive.
I'm starting to suspect that these images may have originated from an Adobe product such as Photoshop CS3 or Illustrator CS3.. since the images that are having issues are from a rather large media department, and only their cases (or other properties they own) seem to be affected.
The problem was that Photoshop saves JPG images in CMYK format but FF and IE don't "get" this image format.
More info: http://www.mattcutts.com/blog/jpeg-problems-in-firefox-and-ie/
This topic is archived. No further replies will be accepted.Other recent topics