But in a quick test, changing the thumbnail image bounds from the default 200x120 to, for example, 100x60, produces thumbnails that are half the size. Make sure you're refreshing your browser cache when previewing the results.
Well, if it looks right when previewed, but not when viewed online, that tells me that you're not uploading the entire album, or you're simply not refreshing your browser cache. Remember, uploading doesn't change anything - it just copies the album that you have just previewed to the server. The album can't magically change during uploading.
And, as always with these JSON-driven skins, make sure you are not telling jAlbum to process only updated subdirectories.
When you make these kinds of changes, you need to process the entire album, and upload the entire album. Trying to pick and choose files to upload won't work.
OK done all of the above and deleted the entire site from the server and reloaded it, cleared the cache etc, and oops its still the same 4 tn's in the preview and 3 big ones in the uploaded site as per the attachments. Still its Sunday... I'll leave it there for today. Many thanks for your help and patience...
Ah, those are folder thumbnails, not regular image thumbnails. We'll have to wait for Laza to check in - I don't see a setting anywhere in the skin that would control the size of those, and they're not being generated by the jAlbum core (the core handles only regular thumbnails and slide images).
The difference between the preview and the website view is caused by a different viewport size - those thumbnails actually change size in response to the size of the viewport.
Maybe later I'll add control for folder thumbnail sizes. Today they are fixed: 320x240 on large monitors, and 192x128 on the smallest. The size varies in between. This is why it's hard to offer a setting for it, because in responsive design it's not the pixel size matters but the visual size.
jGromit, are you saying that stale pages gets cached when previewing? I don't understand why the browser doesn't respect the last modified date (which gets updated properly), but I've now modified jAlbum's preview web server to explicitly deny cacheing. Can you give it a try? Just run a core update to get v19.1.3. This version has a new "Cache-Control" http header (bold):
jGromit, are you saying that stale pages gets cached when previewing?
Yes, I've found the web server preview to be a bit stubborn about allowing the browser to show a cached version. When testing skin changes, I often had to hit CTRL-F5 to shake things loose. In a couple of quick tests, the change in 19.1.3 appears to be much better. I'll keep an eye out for misbehavior.