antoniodlp
Top achievements
Rank 2
Rank 2
antoniodlp
asked on 13 Nov 2007, 05:33 PM
Using the old radEditor, when the property SaveInFile was set to true, the content would save automagically within the ASPX or ASCX file in which the control reside.
Now the SaveInFile property is missing as well as the saving. I can't find anything on the documentation to explain this. What am I doing wrong? Will this behavior be supported in Prometheus?
Thank you
Now the SaveInFile property is missing as well as the saving. I can't find anything on the documentation to explain this. What am I doing wrong? Will this behavior be supported in Prometheus?
Thank you
9 Answers, 1 is accepted
0
Hi Antonio,
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
RadEditor "Prometheus" provides the Content property to set content in its content area. This property gets or sets the text content of the RadEditor control including the HTML markup. You can save the RadEditor content in an external text or HTML file as well as load the content from an external file in the editor.
The following help articles shows how to achieve this:
Kind regards,
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
antoniodlp
Top achievements
Rank 2
Rank 2
answered on 14 Nov 2007, 02:38 PM
Thank you George,
If I understand correctly, the old functionality to save to the very same file the radEditor was embedded in will no longer be available?
What is the purpose of populating the Content property with the <content> tags of the editor then?
This is not too cool as this 'Save In File' functionality was one of the features why we selected your fine controls.
If I understand correctly, the old functionality to save to the very same file the radEditor was embedded in will no longer be available?
What is the purpose of populating the Content property with the <content> tags of the editor then?
This is not too cool as this 'Save In File' functionality was one of the features why we selected your fine controls.
0
Hi Antonio,
We are planing a future build of the RadControls "Prometheus" in the beginning of next week and we will do our best to provide the requested SaveInFile example. As soon as the build is done we will do all you best to inform you.
Kind regards,
George
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
We are planing a future build of the RadControls "Prometheus" in the beginning of next week and we will do our best to provide the requested SaveInFile example. As soon as the build is done we will do all you best to inform you.
Kind regards,
George
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
antoniodlp
Top achievements
Rank 2
Rank 2
answered on 19 Nov 2007, 06:04 PM
Those are great news George, thank you very much.
We can wait until the final release if needed. Just wanted to be sure that functionality wouldn't be lost.
We can wait until the final release if needed. Just wanted to be sure that functionality wouldn't be lost.
0
Hi guys,
We wrote a KB article discussing how to save the RadEditor "Prometheus" content directly in the page with the editor. Here is the link: Saving RadEditor "Prometheus" content directly in the ASPX or ASCX file containing the editor.
We will be glad to receive your feedback!
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
We wrote a KB article discussing how to save the RadEditor "Prometheus" content directly in the page with the editor. Here is the link: Saving RadEditor "Prometheus" content directly in the ASPX or ASCX file containing the editor.
We will be glad to receive your feedback!
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Trent Wheeler
Top achievements
Rank 1
Rank 1
answered on 16 Sep 2008, 11:41 PM
I also require the save in file functionality in RadEditor for Ajax. I've used the code in the example and it works but it inserts a character (Â) plus linebreaks wherever the text was edited. This doesn't show up at editing, but when I then make enabled="false" to view what the public would see, the character is there.
Like the developer who started this thread, the simplicity of the saveinfile property was one of the key features that caused me to purchase this suite over a competitor. In one of the responses something was said about a future build having this functionality again, but it still isn't included. Will this be included anytime soon?
Thanks
Trent
Like the developer who started this thread, the simplicity of the saveinfile property was one of the key features that caused me to purchase this suite over a competitor. In one of the responses something was said about a future build having this functionality again, but it still isn't included. Will this be included anytime soon?
Thanks
Trent
0
Hello Trent,
Having Â's around means that you probably do not save the file with the correct encoding - or, alternatively, you save it in one encoding, but display on a page with a different encoding. Our suggestion is to check and make sure all is saved with the same encoding. In case you are not able to get things working, please open a support ticket and send us a working project that demonstrates the issue and we will look into it.
Regarding building this functionality into the RadEditor - we believe that it should stay out. A KB article has been provided, as well as the editor's code has been changed to facilitate such integration.
Unlike RadEditor Classic, the RadEditor for ASP.NET AJAX is a part of a suite of 23+ other controls that are built on top of MS AJAX. Well established patterns and conventions have been followed for all products in the suite. In the case of the editor this has two implications why the functionality was chosen to stay out:
- The "paradigm" of using RadEditor should be similar to using a <asp:Textbox> or any other input control.
- Various functionality that was less commonly used, but nonetheless built into the editor was causing it to load slowly, and this was the most common reason for dissatisfaction with the RadEditor Classic. BY streamlining the code, and leaving such functionality out (but still possible to integrate, as the KB demonstrates) we managed to reduce the RadEditor for ASP.NET AJAX codebase significantly, and lower the clientside initialization times to 25% of what it previously was (that is, the new editor loads 4 times faster).
I hope this information helps.
All the best,
Tervel
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Having Â's around means that you probably do not save the file with the correct encoding - or, alternatively, you save it in one encoding, but display on a page with a different encoding. Our suggestion is to check and make sure all is saved with the same encoding. In case you are not able to get things working, please open a support ticket and send us a working project that demonstrates the issue and we will look into it.
Regarding building this functionality into the RadEditor - we believe that it should stay out. A KB article has been provided, as well as the editor's code has been changed to facilitate such integration.
Unlike RadEditor Classic, the RadEditor for ASP.NET AJAX is a part of a suite of 23+ other controls that are built on top of MS AJAX. Well established patterns and conventions have been followed for all products in the suite. In the case of the editor this has two implications why the functionality was chosen to stay out:
- The "paradigm" of using RadEditor should be similar to using a <asp:Textbox> or any other input control.
- Various functionality that was less commonly used, but nonetheless built into the editor was causing it to load slowly, and this was the most common reason for dissatisfaction with the RadEditor Classic. BY streamlining the code, and leaving such functionality out (but still possible to integrate, as the KB demonstrates) we managed to reduce the RadEditor for ASP.NET AJAX codebase significantly, and lower the clientside initialization times to 25% of what it previously was (that is, the new editor loads 4 times faster).
I hope this information helps.
All the best,
Tervel
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Trent Wheeler
Top achievements
Rank 1
Rank 1
answered on 19 Sep 2008, 11:33 PM
Sorry I don't know anything about web page encodings. What do I look for to see if this is the problem?
0
Hello Trent,
Here are some links that discuss [file] encoding.
Once again - in case you are not able to resolve your problem, please open a support ticket and send us a working project that demonstrates the issue and we will look into it.
http://support.microsoft.com/kb/893663
http://msdn.microsoft.com/en-us/library/39d1w2xf.aspx
http://weblogs.asp.net/ssadasivuni/archive/2005/01/19/355935.aspx
Best regards,
Tervel
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Here are some links that discuss [file] encoding.
Once again - in case you are not able to resolve your problem, please open a support ticket and send us a working project that demonstrates the issue and we will look into it.
http://support.microsoft.com/kb/893663
http://msdn.microsoft.com/en-us/library/39d1w2xf.aspx
http://weblogs.asp.net/ssadasivuni/archive/2005/01/19/355935.aspx
Best regards,
Tervel
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.