Pages 1
I believe either kb2636573 or kb2492386 has caused any upload over n bytes to fail (currently a 4MB test is failing but smaller files work). Behavior is very similar to a max upload size being too small. Anybody else noticed this?
I haven't seen any other reports of it not working.
Bummer. Well, good for you, bummer for me. I've upgraded to v 3.1.4 on both FileManager and ImageManager. I now see that ImageManager has no problem with the larger uploads, but FileManager still throws a 500 error with no body in the response. I'll keep digging.
Very strange that one of them works and not the other. Are they in different .NET versions/processes?
No, they are in the same app pool. I'm going to run some additional updates that came in from MS and see if that helps. If not I'll keep digging and let you know what I find.
Turns out the upgrade from 3.1.0.1 to 3.1.4 did fix the upload issue. It's working now after reverting back to the default fm theme AND clearing out cache on client (refresh wasn't actually clearing out cached, AJAX'd js files). Gonna run diff's on pages/fm from 3.1.4 and 3.1.0.1 (what I was running previously) and see if something needs to be updated in my theme.
Okay, got it working again.
Note: The problem was only with multi-file uploads. The basic uploader still worked.
It appears that the upgrade from 3.1.0.1 to 3.1.4 fixes the problem introduced by the Windows security update. After that I just had to upgrade my theme to match the changes introduced in pages/fm and make sure that all caches (client side and server side) were totally cleared (a plain ol' refresh didn't cut it).
Last edited by donovan713 (2012-02-03 21:27:57)
Hmm, strange can't remember that we fixed any specific for the .NET backend. Nice that it's fixed though.
Pages 1
You are not logged in. Please login or register.
