30 Jun 2010
28 Sep 2010
Link to this post
Thanks again for your response and video. I have confirmed the behaviour you explain when I run a brand new installation (3.7) on Windows Server 2003 (which is IIS 6). That is, I must have a physical "Images" folder in the root and the images are placed there. All OK.
However, my usual test environment is a desktop which is the relatively old Windows XP with IIS5.1. I am sorry that I did not make this clearer earlier. When I install the exact same brand new installation on my desktop with IIS5.1 I do *NOT* appear to need that "Images" folder. That is, I do the clean install, I do *NOT* create the "images" folder, but I still CAN upload images to the supposed (missing) Images folder. The images DO upload successfully, they CAN be seen in the user interface and when editing the pages and image controls in the administration interface. BUT there is no Images folder in the "files" menu of the administration interface and there is no physical Images folder on the disk when I search in Windows Explorer (it does not even appear to be a hidden or system folder). There is simply no trace of where Sitefinity is placing those images.
So, to recap. Yes, I see exactly what you mean in Windows Server 2003/IIS6. But I do not experience the same behvaiour on XP/IIS5.1. Why is this different? It "works" in IIS5.1 but where is Sitefinity keeping the "Images" folder in an old IIS5.1 environment?
Thanks for your time.