Image/document upload stopped working

[Theron Roe]

After a long weekend, I returned to work today and had a contributor alert me that they could not upload images through the "browse" function onto one of our sites. I went into the user settings to make sure the permissions weren't preventing her, and noticed that I couldn't upload either. Attempting to do so, browsing the network for the file in the browse window and clicking upload, returns you to the upload window without error or adding the file.

I checked another site we have using Savvy (different setup and Db) and found a similar problem with documents and images. This function has worked in the past for both sites, so it's not in the setup.

We do have staff that can bring files directly into the images folder on the Savvy server (they can see the thumbnail in Savvy and can link to it after this), but most staff don't have permissions to the web server and can only access (upload to) that server through Savvy.

Any ideas about what could be causing this?

[Amy Mathews]

You mentioned that these two installs have the same "set up" - are you referring to the same server, or you used the same set of base files? If they are on the same server, I'm wondering if something was set over the weekend that is not allowing the uploads.

[Theron Roe]

Same server, different base files/Savvy setup.

UPDATE: I checked the images folder in Windows Explorer, and the upload IS doing something (though I don't know what exactly)--files ARE being uploaded, but not the image/document format expected. Each time an upload is attempted, a file is created in the destination folder called "KT_NULL" (and KTNULL1, KTNULL2, KTNULL....). I appended one of the KTNULL files with a '.gif' and it is the file I was attempting to upload, just not named correctly. That makes me think it isn't the server settings.

Any ideas how to get this fixed?

[Theron Roe]

Problem solved! I saw on another thread someone was having a different (but similar) problem with image uploading, and Josh mentioned a bug in CF. I updated to CF 8.01 and it is working. Case closed on this one.