I did search for related posts to this but couldn't find anything that seemed similar.
We have written a content management system using RadEditors that enables administrators to edit the content of various sections of their website. In basic terms, if the user is authenticated and authorised they see the full editor and can change the content sections. If they are not authenticated or not authorised they just see the text (not the editor). In the case where they don't have permission we set the Enabled property of the editor to False.
We are using version 2010.1.309.20 and I have yet to try this with the latest version.
We have noticed that when the editor is not Enabled there still appears to be quite a performance hit in the PreRender even though we would have thought that a lot of the processing should not be required as it just needs to display the content and not load any of the editing scripts. This is causing us problems on pages with lots of editors - as every user has the performance hit and not just the admins who are editing the content.
We tried a few examples using different combination of settings on the editor: Enabled=True/False and Visible=True/False.
Below is what we found by using Trace:
Category Message From First(s) From Last(s)
(.Enabled = False .Visible = False) aspx.page End PreRender 0.113901169180098 0.000381
(.Enabled = False .Visible = True) aspx.page End PreRender 0.493980624395962 0.079942
(.Enabled = True .Visible = True) aspx.page End PreRender 0.300766392569965 0.125472
You can see that if the editor is Visible and Editable there is a bit of overhead but this is expected as there is a lot of functionality to load.
But if we set Enabled to False, then there is still quite a hit.
If the editor is not Visible then the hit is minimal.
So we thought about setting the Visible property to False just before the editor's PreRender is fired, and then set it to True straight afterwards. This worked, the non-editable content was displayed on the webpage as normal and the performance hit was minimal.
Is this something that has been addressed in a later version or if not can anything be done so that there is not such a bit hit when the editor is not Enabled.