Andy,

The different thumbnail sizes are generated teh first time they are requested or whenever they are no longer foudn in the cache.

The skin you use for public view of your blog internally decides on which size it wants for the images. A different skin may generate different "thumbnail" sized.

The 80x80 are typically generated when browsing images though the filemanager in the backoffice.

You normally never need to worry about what's in the .evocache folders. It should work completely transparently.

Thanks for the reply. I'm wondering now if I've got something else going on that was leading me in the wrong direction.

What I found is that when I insert an image into the text of a blog post, it prints out html code for the image itself (full-size), as well a making the image a link to itself as well. The software did not use the smaller version specified in the skin (in my case, 420x300) at all. Ultimately that's what I am looking to do, and your post makes it sound like that's a built-in feature that should be working (and isn't).

I messed around with a thumbnail plugin and tried to get it to do the trick, but that didn't go so well. That's when I was poking around with the .evocache, but from what you're saying, I shouldn't even have to worry about doing that manually at all.

Thanks again,
--Andy

Edit:
I just realized how I got the 420x300 images to generate in the first place -- it was by "linking" them to the blog post, rather than just putting them into the middle of the text. Unfortunately we required the flexibility to insert images throughout the text, and linking them forced them to the top of the blog post.

In the absence of the ability to put a "linked" image at a discretionary location in the text, I may have to go back to the plugin I was using and simply use the 80x80 versions as the thumbnails, since those are going to be generated by anyone uploading an image via the uploader.

Yes, the thumbnails are only available when you link an image.

We have plans to be able to insert linked images anywhere in the post but it's not implemented yet.

Well, it took me a while, but I did a very small hack to getfile.php in the htsrv directory.

Where the file manager calls the thumbnail view...

	$File->thumbnail( $size );

I inserted right below it...

	$File->thumbnail( 'fit-400x320' );

...forcing it to create a 400x320 thumbnail as soon as the smaller thumbnail is first viewed/generated -- i.e. immediately after upload.

I modified the thumbnail plugin to hard-link to these 400x320 thumbnails, which fit our needs perfectly.

Thanks for the responses, it did actually set me in the right direction (or at least not to go down the wrong one).