Hi
I've got a page consisting of the Telerik tabstrip control and then the RadMultiPage control with RadPageViews inside of that. I've used the Prometheus AjaxManager to manage the loading of the tabs which works well with the other controls e.g. Pr Combobox, Pr Treeview however when I have the Pr Editor included on one of the tabs I run into problems. The first time the tab is loaded everything is fine. When I then change tab and then go back to the editor tab, I get a javascript error:
Sys.InvalidOperationException: Two components with the same id 'ctl00_contentMain_editTitle_toolbarMode' can't be added to the application
After this, the editor control stops working / rendering correctly.
Is this occuring because of mixing the ASP.Net controls and Prometheus? Any help would be much appreciated.
Thanks
Keith
I've got a page consisting of the Telerik tabstrip control and then the RadMultiPage control with RadPageViews inside of that. I've used the Prometheus AjaxManager to manage the loading of the tabs which works well with the other controls e.g. Pr Combobox, Pr Treeview however when I have the Pr Editor included on one of the tabs I run into problems. The first time the tab is loaded everything is fine. When I then change tab and then go back to the editor tab, I get a javascript error:
Sys.InvalidOperationException: Two components with the same id 'ctl00_contentMain_editTitle_toolbarMode' can't be added to the application
After this, the editor control stops working / rendering correctly.
Is this occuring because of mixing the ASP.Net controls and Prometheus? Any help would be much appreciated.
Thanks
Keith
7 Answers, 1 is accepted
0
Hi Keith,
Just a couple of days ago we had a similar question from another customer. We researched the issue and we found out that setting the <compilation debug="false"> in the web.config causes the exception to disappear.
This is in fact what we recommend you to do as well, since <compilation debug="false"> is the correct setting to use when in production mode - as it speeds execution up and it eliminates a lot of debug-specific MS AJAX code on the client.
If this does not solve the problem, please open a support ticket and send a sample runnable project that demonstrates the problem. I will examine it and try to provide a solution.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Just a couple of days ago we had a similar question from another customer. We researched the issue and we found out that setting the <compilation debug="false"> in the web.config causes the exception to disappear.
This is in fact what we recommend you to do as well, since <compilation debug="false"> is the correct setting to use when in production mode - as it speeds execution up and it eliminates a lot of debug-specific MS AJAX code on the client.
If this does not solve the problem, please open a support ticket and send a sample runnable project that demonstrates the problem. I will examine it and try to provide a solution.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Marcus
Top achievements
Rank 1
answered on 10 Mar 2008, 05:09 AM
Hi there,
I have exactly the same error occurring on my page, although in this case there is no tabstrip. My editor is contained in an UpdatePanel, so I'm guessing this is a cause of the problem.
The suggested workaround is OK for productive websites, but compilation debug="false" is not an appropriate workaround when I am developing, the debug mode is essential for me.
Can you please investigate this issue further and advise? This is occurring with the most recent build of the "Prometheus" RadEditor if that helps.
Let me know if you need further information, but the error message about
"Two components with the same id ...._toolbarMode" is the same for me.
Thanks!
Marcus
0
Hi Marcus,
We will do our best to fix this problem in the upcoming hotfix of the editor. Our suggestion is to temporary disable the debugging with <compilation debug="false"> in the web.config to avoid this error until we fix it.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
We will do our best to fix this problem in the upcoming hotfix of the editor. Our suggestion is to temporary disable the debugging with <compilation debug="false"> in the web.config to avoid this error until we fix it.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
bdk0172
Top achievements
Rank 1
answered on 11 Mar 2008, 07:28 PM
What's the status on the hotfix? I'm in desperate need of this.
0
Hello bdk0172,
The issue is not fixed yet, but it will be surely fixed for the official release of RadControls "Prometheus", due in April.
Here are your temporary options to solve the problem on your side:
Of course this is meant to be just a temporary solution until the problem is fixed.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
The issue is not fixed yet, but it will be surely fixed for the official release of RadControls "Prometheus", due in April.
Here are your temporary options to solve the problem on your side:
- Set the debug property to false in the web.config: <compilation debug="false">
- or set the ToolBarMode property to Default
- or do not place the editor in Ajax UpdatePanel
Of course this is meant to be just a temporary solution until the problem is fixed.
Best regards,
Rumen
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
sara
Top achievements
Rank 1
answered on 25 Mar 2008, 03:44 PM
I have the same problem as the person in the initial post, except I'm using RadControls for ASP.NET. Do you know if a hotfix will be available for those controls?
0
Hi Sara,
We just fixed the reported problem in the "Futures" build of RadControls "Prometheus". You can find how to download it from the following forum sticky note: Q1 2008 "Futures" Build.
In regards to the Classic version of RadEditor, you should not experience the same problem.
Kind regards,
Rumen
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
We just fixed the reported problem in the "Futures" build of RadControls "Prometheus". You can find how to download it from the following forum sticky note: Q1 2008 "Futures" Build.
In regards to the Classic version of RadEditor, you should not experience the same problem.
Kind regards,
Rumen
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center