I've been using RadEditor version 7.x for several years now and have just upgraded to Q2 2010 release.
I was using SaveInFile property but now cannot find a documentation on how to do the same thing with Q2 2010.
Please point me in the right direction. thanks
I was using SaveInFile property but now cannot find a documentation on how to do the same thing with Q2 2010.
Please point me in the right direction. thanks
3 Answers, 1 is accepted
0
Hello Tyler,
You can find information how to implement this functionality in the following help article: Save In File.
Greetings,
Rumen
the Telerik team
You can find information how to implement this functionality in the following help article: Save In File.
Greetings,
Rumen
the Telerik team
Browse the vast support resources we have to jumpstart your development with RadControls for ASP.NET AJAX. See how to integrate our AJAX controls seamlessly in SharePoint 2007/2010 visiting our common SharePoint portal.
0
Tyler
Top achievements
Rank 1
Rank 1
answered on 01 Dec 2010, 03:24 PM
Is there an easier way to do this? In the old version of radEditor I did not have to add any code, just set SaveInFile.
I have over 300 pages that was using this feature. Any reason telerik removed the simple SaveInFile functionality?
I have over 300 pages that was using this feature. Any reason telerik removed the simple SaveInFile functionality?
0
Hello Tyler,
The SaveInFile functionality was a hack into the ASP.NET programming paradigm. This paradigm is simple and well established - one has a form, input controls, and the content from these input controls goes to a database or to some other kind of storage (XML, plain text, etc). While saving directly into file is great for easily producing editable pages in a web-site, the added complexity created confusion on many users who use the "classic" approach to coding a site. The would not understand what some properties do, and why they are needed.
Originally, saving in file was the default option of RadEditor - then at some point later, it was changed to *not* save in file by default. The Ajax suite features editor that was rewritten from the grounds up, as well as following the established programming ASP.NET and MS AJAX paradigms. This is why this functionality needed to go away from the editor.
Since we are well-aware of the convenience of the feature in certain scenarios, we created a Save In File. help article and provided the code - ready to use - for people who wish to migrate from Classic to Ajax suite and wish to continue using this functionality. This code does not need to be pasted on each page - what you could do is subclass the editor and move the SaveInCurrentFile to be a method of RadEditor.
I am sorry if it is creating an inconvenience for you, as we always do our best to fulfill our customers expectations. However, in this particular case the decision was taken with consideration to many factors - last but not least that there are at least several alternatives. As this functionality is a hack, and as it will continue to exist in RadEditor Classic (as it has always been), there are no plans to move it to RadEditor for ASP.NET AJAX at this point.
Best regards,
Rumen
the Telerik team
The SaveInFile functionality was a hack into the ASP.NET programming paradigm. This paradigm is simple and well established - one has a form, input controls, and the content from these input controls goes to a database or to some other kind of storage (XML, plain text, etc). While saving directly into file is great for easily producing editable pages in a web-site, the added complexity created confusion on many users who use the "classic" approach to coding a site. The would not understand what some properties do, and why they are needed.
Originally, saving in file was the default option of RadEditor - then at some point later, it was changed to *not* save in file by default. The Ajax suite features editor that was rewritten from the grounds up, as well as following the established programming ASP.NET and MS AJAX paradigms. This is why this functionality needed to go away from the editor.
Since we are well-aware of the convenience of the feature in certain scenarios, we created a Save In File. help article and provided the code - ready to use - for people who wish to migrate from Classic to Ajax suite and wish to continue using this functionality. This code does not need to be pasted on each page - what you could do is subclass the editor and move the SaveInCurrentFile to be a method of RadEditor.
I am sorry if it is creating an inconvenience for you, as we always do our best to fulfill our customers expectations. However, in this particular case the decision was taken with consideration to many factors - last but not least that there are at least several alternatives. As this functionality is a hack, and as it will continue to exist in RadEditor Classic (as it has always been), there are no plans to move it to RadEditor for ASP.NET AJAX at this point.
Best regards,
Rumen
the Telerik team
Browse the vast support resources we have to jumpstart your development with RadControls for ASP.NET AJAX. See how to integrate our AJAX controls seamlessly in SharePoint 2007/2010 visiting our common SharePoint portal.