This question is locked. New answers and comments are not allowed.
Problem: The content area of the RadEditor control starts off in an uneditable state. Switching to "HTML" edit mode, then back to "Design" mode causes the content area to be editable.
What is the correct way to ensure that the content area of the RadEditor control is editable when the control is created?
Thanks, in advance.
What is the correct way to ensure that the content area of the RadEditor control is editable when the control is created?
Thanks, in advance.
4 Answers, 1 is accepted
0
Hi Glenn,
You can experience this problem if the editor is not loading its script files for some reason or there is a javascript error.
Can you please provide more details about your scenario and provide a sample working project or detailed instructions how to reproduce the issue on our side? You can send a sample project by opening a support ticket. You can also provide a live URL to the problematic page to check for JavaScript errors and debug them.
Best regards,
Rumen
the Telerik team
You can experience this problem if the editor is not loading its script files for some reason or there is a javascript error.
Can you please provide more details about your scenario and provide a sample working project or detailed instructions how to reproduce the issue on our side? You can send a sample project by opening a support ticket. You can also provide a live URL to the problematic page to check for JavaScript errors and debug them.
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.
0
Glenn
Top achievements
Rank 1
Rank 1
answered on 08 Dec 2010, 05:36 PM
Thanks Rumen.
More information
This problem is occurring as a result of upgrading from a (very) old version of RadEditor (version 6.1) to the latest version. There are several instances of the editor being used throughout the application - some have the problem, some do not.
There were no JavaScript errors on any of the affected pages. All instances of the RadEditor are setup by one common section of C# code (but some have the problem and some do not).
Using Internet Explorer's "Developer Tools", I was able to see the BODY tag within the IFRAME of the RadEditor. The instances without the problem have an attribute "contentEditable" with a value of "true" in the BODY tag when it's first created. The instances with the problem have no attributes in the BODY tag. Clicking "HTML" edit mode, then back to "Design" edit mode adds the "contentEditable" attribute to the BODY tag.
Your request for sample code or a website is difficult to provide. The scenerio is an upgrade which is difficult to reproduce in a sample. Also, the development site is inaccessible from the internet.
Is there a specific section of JavaScript that I could look for which affects the editable state of the RadEditor?
More information
This problem is occurring as a result of upgrading from a (very) old version of RadEditor (version 6.1) to the latest version. There are several instances of the editor being used throughout the application - some have the problem, some do not.
There were no JavaScript errors on any of the affected pages. All instances of the RadEditor are setup by one common section of C# code (but some have the problem and some do not).
Using Internet Explorer's "Developer Tools", I was able to see the BODY tag within the IFRAME of the RadEditor. The instances without the problem have an attribute "contentEditable" with a value of "true" in the BODY tag when it's first created. The instances with the problem have no attributes in the BODY tag. Clicking "HTML" edit mode, then back to "Design" edit mode adds the "contentEditable" attribute to the BODY tag.
Your request for sample code or a website is difficult to provide. The scenerio is an upgrade which is difficult to reproduce in a sample. Also, the development site is inaccessible from the internet.
Is there a specific section of JavaScript that I could look for which affects the editable state of the RadEditor?
0
Glenn
Top achievements
Rank 1
Rank 1
answered on 08 Dec 2010, 10:19 PM
Thanks again for your help, Rumen.
I was able to determine the cause of the problem. The ToolsFile.xml file had some settings that seem to be invalid in the new version. Once I removed the entries, the problem was resolved.
I didn't narrow it down to a specific setting, however, the attributes that I removed are:
enabled
visible
dockable
Glenn
0
Hello Glenn,
I am glad that the problem is resolved.
Indeed, the tooltip, title, dockable, enabled and visible attributes should be removed from the ToolsFile.xml file, because they are not supported by RadEditor for ASP.NET AJAX.
Kind regards,
Rumen
the Telerik team
I am glad that the problem is resolved.
Indeed, the tooltip, title, dockable, enabled and visible attributes should be removed from the ToolsFile.xml file, because they are not supported by RadEditor for ASP.NET AJAX.
Kind 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.