This question is locked. New answers and comments are not allowed.
David Noah
Top achievements
Rank 1
Rank 1
David Noah
asked on 09 Oct 2006, 08:41 PM
Hi all,
I have been experimenting with getting radEditor working with WSS V3 B2. The Telerik install instructions "Replacing default rich-text editor" do not work with WSS V3 as MS have changed the scripts file around and seems ows.js is now split up into a number of different .js script files now (the key one being FORM.JS)
I have managed to get radEditor replaced for Tasks, Calendar, Announcement/News lists plus custom lists which use a rich editor-type column.
radEditor also integrates with the User Profile.
What you need to do is:
1. Identify where base WSS LAYOUTS directory is first of all. This is probably C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033\ although may be different on your own system.
2. Edit the file FORM.JS in the above directory.
3. At the end of FORM.JS add the following script code:
/* radEditor PATCH */
//Add custom FORM.JS script to head of every page in the farm
try
{
var head = document.getElementsByTagName("head");
if(head)
{
var script = document.createElement("script");
script.language = "javascript";
script.type = "text/javascript";
script.src = "/ext/scripts/custom/ows_patch.js";
script.defer = true;
head[0].appendChild(script);
}
}
catch(e){ /* ignore */}
what this does is to use the DOM to dynamically load a <SCRIPT> tag to HEAD of every WSS page.
This script tag loads a custom "extension" script file which contains the Telerik integration code.
I prefer to use this "stub" approach rather than adding Telerik script code directly to the MS FORM.JS as it allows you to maintain any extension code
separately (I'm looking at nicer way of doing this by dynamically loading script via window onLoad event handler - will post on this later)
I have setup a new virtual directory called "ext" under the WSS virtual root so that I can store my own scripts, css files outside
the WSS-controlled document space - Note: you will need to add a Path exclusion via Central Admin to do this so WSS does not intercept requests for resources within this directory.
If you want to use another script location, just change the script.src property to point to correct script location.
4. Copy the ows_patch.js file from the radEditor install package to your custom script directory - in example above, I have chosen /ext/scripts/custom/
5. In your web browser, delete any cached files/scripts
6. Point to your WSS site
7. The My Settings > Edit Profile option now uses the radEditor to edit your profile details
7. Any list using the richtext editor will now show the radEditor control rendered inplace of the default one
Regretably, haven't had any luck yet in replacing the editor for 'Basic Web Page' - this uses a completely different script called bpstd.js instead of form.js
If anyone has any joy in getting radEditor replaced for Basic Pages, would love to hear - please email me at david@appliedtechsolutions.co.nz
regards,
Dave Noah
Applied Technology Solutions
http://www.appliedtechsolutions.co.nz
I have been experimenting with getting radEditor working with WSS V3 B2. The Telerik install instructions "Replacing default rich-text editor" do not work with WSS V3 as MS have changed the scripts file around and seems ows.js is now split up into a number of different .js script files now (the key one being FORM.JS)
I have managed to get radEditor replaced for Tasks, Calendar, Announcement/News lists plus custom lists which use a rich editor-type column.
radEditor also integrates with the User Profile.
What you need to do is:
1. Identify where base WSS LAYOUTS directory is first of all. This is probably C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033\ although may be different on your own system.
2. Edit the file FORM.JS in the above directory.
3. At the end of FORM.JS add the following script code:
/* radEditor PATCH */
//Add custom FORM.JS script to head of every page in the farm
try
{
var head = document.getElementsByTagName("head");
if(head)
{
var script = document.createElement("script");
script.language = "javascript";
script.type = "text/javascript";
script.src = "/ext/scripts/custom/ows_patch.js";
script.defer = true;
head[0].appendChild(script);
}
}
catch(e){ /* ignore */}
what this does is to use the DOM to dynamically load a <SCRIPT> tag to HEAD of every WSS page.
This script tag loads a custom "extension" script file which contains the Telerik integration code.
I prefer to use this "stub" approach rather than adding Telerik script code directly to the MS FORM.JS as it allows you to maintain any extension code
separately (I'm looking at nicer way of doing this by dynamically loading script via window onLoad event handler - will post on this later)
I have setup a new virtual directory called "ext" under the WSS virtual root so that I can store my own scripts, css files outside
the WSS-controlled document space - Note: you will need to add a Path exclusion via Central Admin to do this so WSS does not intercept requests for resources within this directory.
If you want to use another script location, just change the script.src property to point to correct script location.
4. Copy the ows_patch.js file from the radEditor install package to your custom script directory - in example above, I have chosen /ext/scripts/custom/
5. In your web browser, delete any cached files/scripts
6. Point to your WSS site
7. The My Settings > Edit Profile option now uses the radEditor to edit your profile details
7. Any list using the richtext editor will now show the radEditor control rendered inplace of the default one
Regretably, haven't had any luck yet in replacing the editor for 'Basic Web Page' - this uses a completely different script called bpstd.js instead of form.js
If anyone has any joy in getting radEditor replaced for Basic Pages, would love to hear - please email me at david@appliedtechsolutions.co.nz
regards,
Dave Noah
Applied Technology Solutions
http://www.appliedtechsolutions.co.nz
4 Answers, 1 is accepted
0
grangel
Top achievements
Rank 1
Rank 1
answered on 10 Oct 2006, 11:21 PM
Great job David! We are really interested in replacing the editor for Wiki and Blog. Have you looked in to that?
0
Hi Gabriel,
We have tested the editor in the new MOSS site types (blog, wiki) and it worked fine. Both the wiki and the blog sites use normal SharePoint forms for editing the content items (wiki pages, blog entries). This scenario is covered by patching the form.js file as described by David. The special functions (for example [[link]] links in the wiki pages) are handled correctly, since they occur on the server, after the editor content has been submitted.
Best wishes,
Lini
the telerik team
We have tested the editor in the new MOSS site types (blog, wiki) and it worked fine. Both the wiki and the blog sites use normal SharePoint forms for editing the content items (wiki pages, blog entries). This scenario is covered by patching the form.js file as described by David. The special functions (for example [[link]] links in the wiki pages) are handled correctly, since they occur on the server, after the editor content has been submitted.
Best wishes,
Lini
the telerik team
0
Keewy
Top achievements
Rank 1
Rank 1
answered on 23 Feb 2007, 02:30 PM
Hi,
We are really interested in changing default rich text editor in wss 3.0 with r.a.d. editor for sharepoint. After release version of r.a.d. editor has been released, the way David has shown us doesn't work anymore. We would like to change every RTE possible with r.a.d. editor including blog and wiki. Let me remind again, we are using wss v3. Is there any way of doing this?
Thanks in advance..
We are really interested in changing default rich text editor in wss 3.0 with r.a.d. editor for sharepoint. After release version of r.a.d. editor has been released, the way David has shown us doesn't work anymore. We would like to change every RTE possible with r.a.d. editor including blog and wiki. Let me remind again, we are using wss v3. Is there any way of doing this?
Thanks in advance..
0
Hello Kerem,
The approach described by David was used to make the WSSv2 radEditor in WSSv3.
The recently released radEditor for MOSS makes this approach obsolete as the MOSS edition works in WSSv3. You can find more info here.
Sincerely yours,
Dimitar Milushev
the telerik team
The approach described by David was used to make the WSSv2 radEditor in WSSv3.
The recently released radEditor for MOSS makes this approach obsolete as the MOSS edition works in WSSv3. You can find more info here.
Sincerely yours,
Dimitar Milushev
the telerik team