Hi,
We are using Telerik AJAX UI control version "2015.3.930.45" in our project. We are using Telerik Image editor in our application and we are facing some issue with the "Save" and "Export" in case if we provide the absolute path to the image editor. But for the images which are in the root of the website itself both of the functionality is working fine. In our case, we can NOT keep the image in the website itself because of the load balancer. So we are assigning path from a separate file server.
Here is the sample code which we are using in our project:
<telerik:RadImageEditor ID="TelerikRadImageEditor" runat="server" ImageUrl="https://<servername>/<folderName>/<fileName>.<extension>" >
</telerik:RadImageEditor>
Save image functionality issue:
Suppose, the file which was shown in the image editor is ".jpg" and user click on "Save Image" icon from the tool bar. After that user select “Download Image” option in “Save Dialog popup” and click “Ok” button then we observer that the saved image have the extension of ".png" even though the file extension which we have given to Image Editor was ".jpg". We have tested the same with the ".jpeg" and ".bmp" but the image which is download via download popup have the ".png".
We don't know why the image is saving with extension ".PNG". This should be saved with the same extension we have given in the image URL.
Do let us know whether its a actual functionality provided by Image editor or its a bug. Also, let us know how we can resolve this issue.
FYI, the said functionality working fine for the local image kept within the website with relative URL.
Export image functionality issue:
When user click on "Export" for the image with the ImageURL from the separate file server then system throws the error and export functionality gets failed. The error message we getting is "not a valid virtual path".
Please help us out to resolve these two issues.
with regards
Abhishek Goel
1 Answer, 1 is accepted
The same matter is discussed here—http://www.telerik.com/forums/save-and-export-tool-not-working. As mentioned there, such scenarios should be handled by using you own, custom Image Content Provider.
Regards,
Ianko
Telerik