We'll try and get these fixed in the next release. The reason that you're not getting an indication of the maximum file size is most likely a Windows installer bug, possibly related to the other ini_get errors (such as the PHP installer not being able to find the memory_limit directive on Windows).

I haven't been able to find a work around yet, but if I turn anything up before the next release, I'll post it here.

This will allow you to upload files up to 10 MB with the extension .jpg. For now, just call this multiple times, once for every kind of file you want to upload.

In the next release, we'll fix this so that the filesize is only limited by PHP, then we can use File::setMaxFileSize() for it's actual purpose.

Sorry for the problems!

Also, I noticed a problem when attempting to view a file in the Files & Images section after it's been uploaded, so I've fixed that. I've posted a new thread about that bug, so if you get a SQL error when you click on a file, check out the fix here:http://www.silverstripe.com/bugs/flat/370?showPost=370

Hi Matt, thanks for the tip and I'm glad to see it helped Peter. I did not stop my installation from having these errors though. It still can't upload images to assets or rename folders. I believe my ISP is running Ubuntu. I used the PHP installer. Any other tips would be much appreciated!

P.S. I'm also receiving the dhtml tooltip error in the lower right corner saying 'nothing to upload'. This happens in both ie7 and firefox 2.

P.S. When I kill the script in AssetAdmin.php and print_r($_FILES) it shows an error 4 meaning "No file was uploaded". Also there is no tmp_file listed.