Question

I am having difficulty with a few gif graphics in TWikiDocGraphics not displaying. In the left tool bar the graphics for Home, Search, Notifications, and Preferences do not display. Other graphics display OK.

When I navigate to the TWikiDocGraphics page about 45 icons do not display and the rest display fine. If I click on any of the attachments to this page, a browser window opens and displays the graphic.

When I look at the files in the F:/twiki/pub/TWiki/TWikiDocGraphics directory the non displaying files are present and can be opened. When I examine the properties of the files, the ones that don't display look the same as the ones that do.

I don't think its a browser issue because I have two TWiki systems (one on a Windows XP machine and one on Win 2000 Professional). The XP one works fine and displays all graphics all the time. The Win 2K installation doesn't show me the 45 graphics using MSIE 7 but shows all graphics to other users using both MSIE 6 and 7.

I have compared the Apache and TWiki config files for both implementations and found them to be identical.

I have checked the bin/configure settings for everything to do with pub and believe them to be OK.

I have created test pages with code that displays the note.gif icon and it displays fine. When I change note.fig to book.gif, the graphics won't display. The code I used for the test pages is as follows

Can you advise where else to look for a cause/solution? Thanks

Environment

-- JimCrum - 27 Feb 2007

Answer

If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.

This same issue as described above also happens with the Firefox 2.0.0.2 browser. Therefore, I am suspecting the interaction between TWiki and Apache???

-- JimCrum - 28 Feb 2007

Closed for lack of interest

-- JimCrum - 26 Mar 2007

Wild guess: Could be related to case sensitivity? If one installation is set up to be case sensitive and some filenames are somehow in UPPERCASE, this might be the cause.

Anyway, try to install a utility in the browsers (alternatively setup a local proxy) that will dump the exact GET requests and responses - that should make any differences easily inspectable.

-- SteffenPoulsen - 26 Mar 2007