...the cache must be cleared for the user to see the changed theme image.
It's not just the theme image. Without refreshing cache, visitors might be seeing old thumbnails, old titles, and so on.
My current workaround is to rename ja-theme.jpg to ja-theme21.jpg (today's date) and editing the links in index.html and infopage.html. It's a little clunky but seems to get the job done. I'm wondering if this method is OK or is there a better, easier solution.
For the theme image, that will certainly work, but I wouldn't want to saddle myself with that kind of ongoing manual tinkering.
Thoughts?
You need to keep beating on your visitors to hit F5 or CTRL-F5 once in a while. Anyone who doesn't do that habitually is at risk of seeing stale content, and not just on jAlbum album pages.
The center logo displays lower on the screen even though there should be enough space between the navleft & navright icons, even when in portrait orientation.
I actually prefer the appearance with the logo set down, rather than plastered against the top of the browser window, even on a desktop. But...
The skin can't really anticipate what device is going to be used, and, more important, what nav icons there might be up there, including things like external links, folder menus, up arrows, music icons, and so on. All it can safely do on a small screen is float the nav elements and move the logo down to avoid collisions.
But in this case, since you're not loading up the nav boxes with stuff, and your logo is small, you can just brute-force it:
.ja-logo {padding-top: 0px !important;}
That will override the script that runs at display time. The downside is that, on a page that
does have other nav icons, the logo might not be centered, as in the attached screenshot. If I were you, I'd just let the logo move down, as designed.
