The 1.2 version has problems with identifying MimeTypes and ContentTypes of images and certain files and is also caused because WSL uses the wrong Encoding for the image data in the stream.
I assure these are already fixed in my local 1.3 version but I still don't know when I'll havetime to finish it, it's a huge project for just one person to handle.
I'm in and out of hospital atm and I have a lot of other projects going on that (I hate to say it) take priority over this because they are bringing in extra money :S
Suffice to say, WSL 1.3 will definitely get completed and I'm proud of the patience of the community in wiating for this release because I know it will benefit everyone a great deal.
Thanks for your time and patience (again)
PS.
You can attempt to fix the borken images yourself by fixing the Utilities/MimeTypes.cs script, because I think that's what's failing with images...
Before any WebObject is output to the stream, the ContentType is set, by default it's "Text/Plain" and for a JPEG image it should be "Image/Jpeg", but the MimeType handler seems to be broken, therefore your browser thinks that images are plain-text, unless you explicitly set it yourself.
The MimeTypes handler's job is to check and set the default MimeType of EVERY WebObject.
The MimeTypes detection script is a piece of work that I didn't write, I merely grabbed the code and modified it to work with WSL, so it looks like I'll have to overhaul the whole thing for 1.3 (even though the issue is resolved, there's no need to keep bloated code)
PPS
I just did some testing with 1.2 Stable-BETA and everything is working fine.
I *was* able to re-create your problem in a certain way:
When WSL starts up, if it encounters any errors during the gathering and compilation of WebObjects, then *no* web-objects will be loaded into WSL *at all* which means you'll get nothing but failed requests for any *virtual* WebObject.
I will improve to compilation system for 1.3 in such a way that it will use the process of elimination and re-compiling to ensure that even errors will not disturb the initialization and registration of WebObjects and other WSL modules.
Thanks for your time.