sassymonkey
Forum Replies Created
-
Like a few others in this looooong thread, I fixed this problem by only changing one thing: I somehow had “/wp-content/uploads” instead of the default “wp-content/uploads” in the Settings -> Miscellaneous -> “Store uploads in this folder” field.
Funny thing though: all the while I was getting the errors, I kept getting complaints about no access to the wrong date folder (2008/11). It should have been complaining about no access to the current year and month (2009/03).
Once I removed the initial “/”, the upload worked and, sure enough, it put the file into 2008/11. Yet, it created a new folder in 2009/03 but didn’t put it there in favor of 2008/11!
Strange. It’s annoying and will probably cause me some future neck-pain but at least it’s working.
Forum: Alpha/Beta/RC
In reply to: [Plugin: NextGEN Gallery] Squished ThumbnailsIndeed, the squished thumbnail problem does NOT exist in both the default theme and the Classic. BTW, the theme I’m using is called “Maple Leaf” available at TemplateLite.com.
This makes me think there’s something in my theme’s CSS that is affecting NextGen (like maybe an a: or hover: class). This is not the case though. I looked at the various divs that NextGen creates to display thumbnails and they are all uniquely labeled and should not conflict with my theme’s CSS. I also removed a bunch of CSS bits that might affect it with no changes.
One consistency I did find in Safari is that simply loading a gallery page with thumbnails will nearly always show the squish problem. However, if I click the [Slideshow] link to switch over the the Flash viewer, and then switch back by clicking the [Picture List] link, the thumbnails nearly ALWAYS show up correctly.
Yet, this is only on Safari. Goggle’s Chrome always shows them squished regardless.
Very puzzling. I’m at a loss of where to start eliminating code to see if anything affects it.
Forum: Alpha/Beta/RC
In reply to: [Plugin: NextGEN Gallery] Squished ThumbnailsBTW, the same problem is happening in Google’s Chrome browser. I assume that since both Safari and Chrome are using the WebKit rendering engine, therein lies the problem: something about the coding in NextGen for the thumbnails is incompatible with WebKit.
Seeing as how Chrome is already garnering a user base (cnet reported recently that it’s already the fourth most used browser to visit their sites), and seeing as how Safari is well established, maybe this display problem can be tackled sooner rather than later… maybe? C|:-}