2 Answers, 1 is accepted
0
WAB
Top achievements
Rank 1
Rank 1
answered on 25 Jul 2007, 11:25 PM
I guess what I'm getting at is this:
The first example in the help file is for replacing a webpart - not a very elegant solution for a site that uses a wiki, for example, which we do use.
The second example in the help file is for replacing the editor in the Web Content Management scenario. If I understand this implementation correctly, then the page is created first then the control is regsitered and then reference to the moss editor control added (replacing PublishingWebControls:RichHtmlField with radE:RadHtmlField from the help file).
For this to be feasible we need a way for new pages that are created to automatically reference the new control via the second example above. Something seamless. I'm not referring at all to old content being associated to the new control since this is a brand new site we'll be using with no associated content.
An example - If I go to our wiki and add a wiki page, I expect the new wiki page to contain the MOSS rad editor control as the default editor without changing anything.
Hopefully, that makes sense.
The first example in the help file is for replacing a webpart - not a very elegant solution for a site that uses a wiki, for example, which we do use.
The second example in the help file is for replacing the editor in the Web Content Management scenario. If I understand this implementation correctly, then the page is created first then the control is regsitered and then reference to the moss editor control added (replacing PublishingWebControls:RichHtmlField with radE:RadHtmlField from the help file).
For this to be feasible we need a way for new pages that are created to automatically reference the new control via the second example above. Something seamless. I'm not referring at all to old content being associated to the new control since this is a brand new site we'll be using with no associated content.
An example - If I go to our wiki and add a wiki page, I expect the new wiki page to contain the MOSS rad editor control as the default editor without changing anything.
Hopefully, that makes sense.
0
Hi,
Wikis and blogs in MOSS are represented internally as lists. This means that if you want to use RadEditor in wikis, you need to look at the lists scenario. Replacing the default editor for Wikis on a site is easy - just go to the site settings page, open the site features and enable the two RadEditor features. All existing and new wiki pages will use the RadEditor after that. If you do not see our editor right away, you might need to recycle the SharePoint web application (sometimes it caches the old editor).
Sincerely yours,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Wikis and blogs in MOSS are represented internally as lists. This means that if you want to use RadEditor in wikis, you need to look at the lists scenario. Replacing the default editor for Wikis on a site is easy - just go to the site settings page, open the site features and enable the two RadEditor features. All existing and new wiki pages will use the RadEditor after that. If you do not see our editor right away, you might need to recycle the SharePoint web application (sometimes it caches the old editor).
Sincerely yours,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center