Paul Haines
Top achievements
Rank 1
Rank 1
Paul Haines
asked on 18 Feb 2009, 10:42 AM
After upgrading to the "prometheus" version of the RadEditor there's still some older properties that we haven't found information about what they've been changed to. Perhaps someone from telerik could explain what the following properties are now, (or if they've been completely removed);
1) ConvertToXhtml.
2) EnableClientSerialize.
3) DocumentsFilters.
4) EnableContextMenus.
5) EnableDocking.
6) EnableEnhancedEdit.
7) EnableHtmlIndentation.
8) EnableServerSideRendering.
9) EnableTab.
10) PassSessionData.
11) RenderAsTextArea.
12) SpellEditDistance.
13) TemplateFilters.
14) ImagesFilters.
15) MediaFilters.
Thanks for any information you can supply.
Paul
1) ConvertToXhtml.
2) EnableClientSerialize.
3) DocumentsFilters.
4) EnableContextMenus.
5) EnableDocking.
6) EnableEnhancedEdit.
7) EnableHtmlIndentation.
8) EnableServerSideRendering.
9) EnableTab.
10) PassSessionData.
11) RenderAsTextArea.
12) SpellEditDistance.
13) TemplateFilters.
14) ImagesFilters.
15) MediaFilters.
Thanks for any information you can supply.
Paul
3 Answers, 1 is accepted
0
Hi Paul,
Please, see the following help article on the subject: Migration from RadEditor Classic to RadEditor for ASP.NET AJAX. This article provides migration instructions and information about the changed or obsolete properties.
Let me know if you need any further help.
Kind regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Please, see the following help article on the subject: Migration from RadEditor Classic to RadEditor for ASP.NET AJAX. This article provides migration instructions and information about the changed or obsolete properties.
Let me know if you need any further help.
Kind regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Paul Haines
Top achievements
Rank 1
Rank 1
answered on 18 Feb 2009, 02:51 PM
I have already used that page for our upgrade. The properties listed are those that weren't included there, and I haven't been able to find any other references to.
0
Accepted
Hi Paul,
Please, find below the requested information:
1) ConvertToXhtml - this filter is enabled by default. If needed you can disable it by setting RadEditor1.DisableFilter(EditorFilters.ConvertToXhtml);. You can find more information here.
2) EnableClientSerialize - this property stored the docking position of the toolbars. For better performance we have removed this property but you can configure the toolbar position on the server via the DockingZone property.
3) DocumentsFilters - see the following articles: File Browser Dialogs and Documents.
4) EnableContextMenus - removed for better performance. If needed I can provide you sample code to disable the context menus of RadEditor on the client.
5) EnableDocking - this feature is not supported for the time being.
6) EnableEnhancedEdit - This was used to apply some css to the content area for example whether to see the table and form elements borders. You can achieve this feature by setting the ContentAreaCssFile property to point to an empty css file or css file with the desired css classes that you want to apply to the content area.
7) EnableHtmlIndentation - this filter is enabled by default. You can disable it by setting RadEditor1.DisableFilter(EditorFilters.IndentHTMLContent);
8) EnableServerSideRendering - the new editor has a very fast rendering and this property was removed
9) EnableTab - removed. If you want to achieve the same functionality I can send you javascript code.
10) PassSessionData - RadEditor uses a new enhanced mechanism for its dialogs and this property was removed.
11) RenderAsTextArea - removed. If you need to render the editor as a textbox, just use a standard asp:TextBox control instead of the editor.
12) SpellEditDistance - use the new SpellCheckSettings-EditDistance property.
13) TemplateFilters - see Templates.
14) ImagesFilters - see Images.
15) MediaFilters - see Media.
Do you experience any problem with the new RadEditor for ASP.NET AJAX?
It is tuned up on the max as well as much developer-friendly because we have removed all properties that are not needed to optimize its configuration and speed.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Please, find below the requested information:
1) ConvertToXhtml - this filter is enabled by default. If needed you can disable it by setting RadEditor1.DisableFilter(EditorFilters.ConvertToXhtml);. You can find more information here.
2) EnableClientSerialize - this property stored the docking position of the toolbars. For better performance we have removed this property but you can configure the toolbar position on the server via the DockingZone property.
3) DocumentsFilters - see the following articles: File Browser Dialogs and Documents.
4) EnableContextMenus - removed for better performance. If needed I can provide you sample code to disable the context menus of RadEditor on the client.
5) EnableDocking - this feature is not supported for the time being.
6) EnableEnhancedEdit - This was used to apply some css to the content area for example whether to see the table and form elements borders. You can achieve this feature by setting the ContentAreaCssFile property to point to an empty css file or css file with the desired css classes that you want to apply to the content area.
7) EnableHtmlIndentation - this filter is enabled by default. You can disable it by setting RadEditor1.DisableFilter(EditorFilters.IndentHTMLContent);
8) EnableServerSideRendering - the new editor has a very fast rendering and this property was removed
9) EnableTab - removed. If you want to achieve the same functionality I can send you javascript code.
10) PassSessionData - RadEditor uses a new enhanced mechanism for its dialogs and this property was removed.
11) RenderAsTextArea - removed. If you need to render the editor as a textbox, just use a standard asp:TextBox control instead of the editor.
12) SpellEditDistance - use the new SpellCheckSettings-EditDistance property.
13) TemplateFilters - see Templates.
14) ImagesFilters - see Images.
15) MediaFilters - see Media.
Do you experience any problem with the new RadEditor for ASP.NET AJAX?
It is tuned up on the max as well as much developer-friendly because we have removed all properties that are not needed to optimize its configuration and speed.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.