When I upload new image the image is uploaded, but after the upload the ImageManager refreshes and display the warning that the same filename allreday exists: "A file with a name same as the target already exists!".
How can I prevent this? I don't have a file with the same name. I thing that the problem is in refreshing that is happening after upload.
9 Answers, 1 is accepted
Can you reproduce the same with this online demo—http://demos.telerik.com/aspnet-ajax/editor/examples/overview/defaultcs.aspx?
If so, please, provide the exact steps-to-reproduce.
The demo works, but on my side I get the above issue. I feel I forgot to include some setting. Here's what I've done:
- put dlls to bin folder
- put http handlers to web.config
- put this in web.config (because I'm suing authetnication):
Am I missing something ?
Configuration seems to be OK. Also, as far as the dialog is opening and files are being uploaded successfully I can only guess what the problem is.
Can you isolate this issue into a simple, locally runnable project and attach it here so to examine this locally?
Thank you for the provided project. I tested it but was able to upload files without any error messages thrown. Can you take a look at the video from my test and see whether I am missing anything? - http://screencast.com/t/0GaygKb35P
Are you reproducing the issue in all browsers or only in a specific one? which is its version?
Looking forward to your reply,
Thanks for reviewing my problem. I see that on your machine everything works as expected. I guess something is wrong with my IIS configuration?? And also, I noticed another problem, when I tick "overwrite" checkbox I got another error. Please take a look at my screen recording here: http://www.dalija.net/unitled.avi
I watched the prepared by you video and it leads me to the assumption that the application does not enough rights to write inside the RadUploadTemp folder. Can you, please, make sure that the project is granted with all permissions to access and edit the App_Data folder?
You can find useful the test approach described in this help article: Testing permissions to a folder
I did not resolve this issue. The app_data folder has full premissions and the test code did run without any exceptions.
What else could be wrong ?
Thank you for the update. Unfortunately we are not aware of other possible reasons for such behavior and will need to examine it on our side in order to be able to provide you with any further assistance. Can you, please, try to isolate the problematic configuration into a runnable sample reproducing the case and send it for a further investigation? It would be helpful also if can give us a live URL where we can examine the exact issue at hand.