This question is locked. New answers and comments are not allowed.
Kurt Rolland
Top achievements
Rank 1
Rank 1
Kurt Rolland
asked on 06 Sep 2006, 08:43 PM
Does this new edition support Windows SharePoint Services v3?
3 Answers, 1 is accepted
0
Hi Kurt,
We are currently testing the new SPS version with the latest MOSS beta and the editor web part seems to be working fine (minus a few glitches).
Here is the current status for the editor web part:
- you need to add the editor web part to the GAC or run the MOSS website with "full" trust level. Note that you need to change the trust level for each site where you need the editor - e.g. the home site, the personal site etc.
- the default editor for page content is not getting replaced with a r.a.d.editor yet (this is normal, since this editor was not available in SPS 2003)
- cross browser support is not complete - the editor works cross browser as a web part and in the user profiles. However, when editing MOSS lists, r.a.d.editor is only available under IE. With other browsers you will still get a normal text box.
If you would like to try the new beta on your MOSS site, you can install it virtually in the same way as in a SPS 2003 site (using the stsadm command line utility). If you also want to use the editor in profiles and lists, you would need to patch the FORM.JS file, located in the C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033 folder. I am attaching the patch to this message. Just extract the file and paste its contents at the end of the FORM.JS file.
Kind regards,
Lini
the telerik team
We are currently testing the new SPS version with the latest MOSS beta and the editor web part seems to be working fine (minus a few glitches).
Here is the current status for the editor web part:
- you need to add the editor web part to the GAC or run the MOSS website with "full" trust level. Note that you need to change the trust level for each site where you need the editor - e.g. the home site, the personal site etc.
- the default editor for page content is not getting replaced with a r.a.d.editor yet (this is normal, since this editor was not available in SPS 2003)
- cross browser support is not complete - the editor works cross browser as a web part and in the user profiles. However, when editing MOSS lists, r.a.d.editor is only available under IE. With other browsers you will still get a normal text box.
If you would like to try the new beta on your MOSS site, you can install it virtually in the same way as in a SPS 2003 site (using the stsadm command line utility). If you also want to use the editor in profiles and lists, you would need to patch the FORM.JS file, located in the C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033 folder. I am attaching the patch to this message. Just extract the file and paste its contents at the end of the FORM.JS file.
Kind regards,
Lini
the telerik team
0
Kurt Rolland
Top achievements
Rank 1
Rank 1
answered on 07 Sep 2006, 11:49 AM
Thanks, I plan on demonstrating at our upcoming SharePoint User's Group meeting this Monday (www.stlsug.org). Any suggestions for demonstration would be appreciated.
0
Hello Kurt,
I am sorry for the delayed reply. I will list the main advantages of our editor, compared with the standart MOSS editor.
1) cross-browser support - We have tested the editor web part in multiple browsers, including FireFox, Safari, Netscape, etc.
2) Ability to edit content directly in the page - you can edit the web part content in a popup window (like the default editor) or directly inside the page.
3) Skin support - you can change the editor's skin with a single property.
4) More HTML editing tools and modules - XHTML validation, tag inspector, etc. You can read more about those on the editor features page - http://www.telerik.com/asp-net-controls/online-wysiwyg-editor/features.aspx
Regards,
Lini
the telerik team
I am sorry for the delayed reply. I will list the main advantages of our editor, compared with the standart MOSS editor.
1) cross-browser support - We have tested the editor web part in multiple browsers, including FireFox, Safari, Netscape, etc.
2) Ability to edit content directly in the page - you can edit the web part content in a popup window (like the default editor) or directly inside the page.
3) Skin support - you can change the editor's skin with a single property.
4) More HTML editing tools and modules - XHTML validation, tag inspector, etc. You can read more about those on the editor features page - http://www.telerik.com/asp-net-controls/online-wysiwyg-editor/features.aspx
Regards,
Lini
the telerik team