Bugzilla – Bug 4179
Fishbone skin killed Safari 2.0.4 usefulness with Slimserver 6.5
Last modified: 2006-09-25 13:23:08 UTC
In anticipation of receiving my Transporter, I upgraded to the official 6.5 release of SS. At first all was well. The default skin was kind of ugly in 6.5, mainly black text on full white background. No tonality. So I switched to Fishbone, That worked fine, but some of the dark grey text was difficult to read, so I reverted to the Default skin. This is where the fun started. The layout of the skin like default, but the background color stayed black. The uppermost drop down menu of any settings selection (Basic settings, etc.) was inaccesible. The right pane was squeezed down to a small area. I then deleted all Slimserver files (I think; ~Library/SlimDevices, ~Library/Caches/Slimserver, ~Library/Preferences/com.slimdevices.slim.plist, ~Library/PreferencePanes/SlimServer.prefPane). I restarted and re-installed SS v6.5.0. Same thing. I repeated this procedure and deleted all possible cookies. Same again. I then pulled a backup of all these file circa v6.3.1 from a recent backup, restarted, and everything was fine again. I then re-upgraded to v6.5.0 and the problem was back. I then accessed SlimServer with Firefox, and the page displayed properly. Safari again - corrupt. Where is the layout in v6.5.0 stored? I have a screenshot of SS in Safari, but I�m not sure how to send it and have it relate to this report. Do you need it? My system is: G4 AGP SP/ Giga Designs 2GHz CPU 896 MB RAM OS X 10.4.7 Any ideas? I would much rather use Safari as the web interface is not very pretty in Firefox. Julius
this sounds like a caching issue, and I'm sorry to say that it sounds like Fishbone skin has little to do with it. I cannot test with safari 2.0.4, but have tested with 1.3.2 which works fine. The skins all use css, with shared code for as much as possible. So, if you change prefs you dod have to deal with caching issues. one workaround is to use the override urls: http://<serverip>:9000/<skinname> so try http://localhost:9000/Default/ this will force caching for the skin name, and not share caches. otherwise, several repeated browser refreshes will usually do the trick.
Julius, did KDF's suggestions help out?
Yes it did. With everything I attempted to solve the problem, clearing the cache was the only thing I neglected to do:-( While I haven�t tried to use the Fishbone skin again, the default skin is now properly displayed and has been stable. Thanks for the suggestion.