An exception after upload image
The problem is appeared today. It was never occured earlier.
So, I upload a new image in album. After that I check album's images: new image is not displayed.
See attachment 1: new image is on the right side.
Then I check "Embed image" field, copy URL and paste it to browser. I expect the picture but I see an exception (see attacment 2).
How can I get rid of this problem?
Hello Anatoliy Gerasin,
Can you please provide me with some more information regarding how this issue originated? Is it possible for you to try and upload another image to the same album and/or another album and tell me if the same issue reproduces?
the Telerik team
I go to /Sitefinity/Content/Images/ page.
Click "Create an album"
Write "Test album" for "Album name" field.
Click "Create this ablum"
Images page is loading. I select "Test album" in "Images by Album" block on the sidebar.
Click "Upload images"
Click "Select images"
Select an image which already been uploaded on the site earlier (to exclude bad image possibility)
Select "Test album" for "Where to store the uploaded Images?" field.
Click "View all images"
See screenshot "noimage3"
Click "Embed image"
Copy value from field "Link (paste in email or IM)"
Paste it into new browser window
See an exception described in 1st post...
Thank you for getting back to me. Did you change something in the IIS configuration prior to this error occurring. If I get you right, populating albums with images was working fine on that project? Can you please try this with a new empty project and confirm if the problem reproduces there, as well? If yes, please take a look at this article from our Installation and Administration guide and make sure you have everything set up according to the instructions there.
the Telerik team
Thank you to the tip about IIS settings.
I tried to enable/disable last web.config changes and have found guilty setting. It's the workaround from this topic:
I had a problem with database connection. "Invalid operation. The connection is closed" was occured periodically.
For now, I've got rid of this workaround and seems that subj is resolved.
But I'm afraid of "connection is closed" problem to be return again...