This is a migrated thread and some comments may be shown as answers.

Important Info

39 Answers 1569 Views

WebParts for SharePoint

This is a migrated thread and some comments may be shown as answers.

Telerik Admin asked on 19 Feb 2007, 05:30 PM

Thank you for choosing telerik r.a.d.editor for SharePoint 2007 (MOSS).

r.a.d.editor MOSS is intended to be a cross-browser alternative to the default rich-text editor in MOSS and WSS v3. The product is developed in an agreement between telerik and Microsoft and is provided free of charged to registered clients of SharePoint 2007.

Important details:

r.a.d.editor for MOSS is provided as is and is not designed to be customizable. There are, however, certain possibilities for minor customization, which are discussed in the How-to section of the "Deployment and configuration manual".

r.a.d.editor for MOSS is a modified version of the telerik r.a.d.editor for ASP.NET. As a result, there are numerous functional differences, which are discussed in a separate document - Feature Comparison.

When r.a.d.editor for MOSS is used for as a rich-text field control in SharePoint forms, it will be displayed only on non-Internet Explorer browsers (see also "Browser support and limitations"). The default Microsoft rich-text editor will be displayed on Internet Explorer.

Support resources:

r.a.d.editor for MOSS is supported through this public forum

online and downloadable documentation (Deployment, Migration, How-to, FAQ)

Feature Comparison sheet

Sincerely yours,
the telerik team

39 Answers, 1 is accepted

answered on 20 Feb 2007, 06:24 PM

I am dissapointed that Telerik was apparently convinced to dumb-down the editor to reduce the capability to that in the default Microsoft MOSS HTML editor. This makes it very hard for me to find any justification for adding complexity to the MOSS environment by adding a different editor. Its main strong point is that it costs nothing. You often get what you pay for.

Does Telerik have plans to provide a full (full from Telerik's point of view) editor for the MOSS environment at some cost?

I've been very happy with the Premium Editor for MCMS 2002 and it is a shame that the current direction with MOSS is to eliminate a number of features.

answered on 21 Feb 2007, 01:02 PM

Why that #3 restriction? ("When r.a.d.editor for MOSS is used for as a rich-text field control in SharePoint forms, it will be displayed only on non-Internet Explorer browsers (see also "Browser support and limitations").

I was hoping to enrich the default "Add Picture" functionality for a rich text field in a list item with a better browse-for-pictures capability - more like the one available for Publishing Pages. However, I can only get that with non-IE browsers.

I don't intend to complain about a free product ;o), but the key point of this product is to enable cross-browser editing, yet it introduces another browser-dependent feature set. Hope for a premium version or something like that!

answered on 21 Feb 2007, 01:45 PM

I have to agree with the other posts i've seen here in that the "dumbing down" of the editor is very disappointing. The main reason for it's use was to provide functionality above and beyond what Microsoft offered and would produce more accessible output.

It is going to be hard to justify it's inlcusion within client solutions for this reason and the issue of supporting it now there seems to be less advantages.

One thing that is stopping it's use on a project i am currently working on is that it seems that the insert image dialogue only allows the selection of an asset within the current SharePoint web. I have tried setting the default image and asset location properties, but it seems to have no effect.

Is this a design fault or feature?

Many Thanks for any Feedback.
Jason Flowers
Trinity Expert Sytems

answered on 22 Feb 2007, 12:46 PM

Hi,

Thank you for providing this initial feedback.

Your questions and concerns clearly make sense so we will try to address them individually and throw a little light regarding our plans for MOSS product development:

r.a.d.editor for MOSS on IE – our agreement with Microsoft is to develop a cross-browser alternative for the default editor. Apparently, SharePoint 2007 is cross-browser, except for the rich-text editor, so we are supposed to cover for the non-IE cases. We will discuss the option for making the r.a.d.editor override the default rich-text editor on IE as well. If we get their permission to do so it will be just a matter of removing one browser check.
Restricted feature set – having in mind point 1 above, the intent behind r.a.d.editor for MOSS was to replicate the functionality of the default IE editor as closely as possible so that there is not much difference in the user experience on the different browsers.
Our presumption is that the default editor in MOSS is quite good in this release, so we considered that most customers would be happy. Your feedback in this respect will be immensely valuable:
- what specific functionality that is only available in the regular r.a.d.editor for ASP.NET do you need?
- in which scenarios do you find further customization capabilities – WebPart or WCM scenario?
At this moment we can't commit to a specific timeframe for providing full-blown editor for MOSS, since we need to determine the level of SharePoint-specific modifications we need to make vs. the level of customization that you would require.
We have always aimed to address customer requests and this free MOSS editor is just the first step. In order to go further we will need some more specific feedback.
Other components from the r.a.d.controls suite and MOSS – our plans with respect to other r.a.d.controls are to provide a whitepaper that describes how you can integrate other telerik controls in MOSS. Unlike the r.a.d.editor where code modifications are necessary, the integration of the regular ASP.NET versions of the r.a.d.controls and their customization with the SharePoint Designer is pretty trivial. Those guides are soon to be prepared and made available online.

Once again, we will appreciate further feedback that can shape the best direction for further MOSS development.

Greetings,

Ivo
the telerik team

www.telerik.com | dnn.telerik.com | www.sharepointcontrols.com | www.sitefinity.com | www.mcmscontrols.com

answered on 22 Feb 2007, 01:54 PM

Ok - I have the following situation:

- The CMS (or "WCM") page editing in MOSS for Publishing Pages is no "silver bullet", in my opinion. Working with users on this, the most common reaction I get is: "it seems messy".

So, I was looking for a simpler way to publish News items. I tried using an "Announcement" list, but the default rich text editor is limited, compared to the one used for Publishing Pages. E.g. there is no "browse-for-pictures" capability. The user has to know the URL to link to, to insert a picture (or a link). This alone is enough for me to NOT use an announcement list as a replacement for News pages. I was hoping that Telerik RADeditor for MOSS did what it used to do under SPS2003 - also replaced the default rich text editor for list items, but no - only for non-IE browsers.

I also think editing tables in the built-in editor for publishing pages is akward.

Finally, a better way to provide custom styles for formatting. Out-of-the-box, you have to edit a file directly on the web server(s), and this is generally not a best practise for other types of MOSS-files. It would be better if we could use CSS styles from a file in e.g. the Style Library or any other document library for that matter. And while we're at it - why not display the all styles as they will look, rather than simple titles. WYSIWYG is expected these days.

These are my suggestions!

answered on 27 Feb 2007, 07:24 PM

I would like to strongly encourage Telerik to continue working with Microsoft to get permissions to let us override the default editor with the Telerik Editor for SharePoint for all browsers. I very much prefer your editor to the default editor in SharePoint lists and do not in any way agree that it 'hurts more than helps.' The default editor is not acceptable, primarily because it does not let you select images and links that you've already added to the SharePoint site, and worst of all, it requires users to know html be be able to set the target for a link. (Setting links to open in a new window is one of the most frustrating omissions in SharePoint 2007.)

Keep up the great work. The features provided by the Telerik Editor for SharePoint are so important that I would not have any problem whatsoever paying for them.

Joel

answered on 01 Mar 2007, 11:50 AM

Thank you all for the feedback. It is much appreciated.

Let me shed some light on our latest discussions with Microsoft and our plans for the coming months.

IE support
In the next update of the free MOSS editor (next month) we will provide the option to edit SharePoint lists with r.a.d.editor in IE as well. Microsoft has agreed that we can provide a setting which enables r.a.d.editor on IE as long as the default behavior is kept as it is now (r.a.d.editor is enabled only on non-IE browsers and Microsoft editor is enabled in IE)

Full featured editor
We are planning for a release of a full featured r.a.d.editor for MOSS in about 4-6 weeks. The full featured editor for MOSS will allow for a broad feature-set and a flexible customization similar to our previous offerings: MCMS Premium Placeholder and SharePoint 2003 Editor. All customers willing to use the full featured MOSS editor will need a valid license for r.a.d.editor (http://www.telerik.com/purchase/purchase-online/b200S-dhe.aspx ). Comprehensive MOSS-specific documentation will be provided on how to use and customize all features. Public Beta version will be shipped to collect feedback before the official release.

WSS v3
The current version of r.a.d.editor for MOSS can safely be used in WSS v3 as well. Both Lists and Web Parts scenarios are supported.

Please, let us know of your comments and suggestions -- they will be very welcome.

Ivo
the telerik team

www.telerik.com | dnn.telerik.com | www.sitefinity.com

answered on 12 Mar 2007, 12:42 AM

I find this extremely dissapointing. We are currently doing a proof of concept for MOSS and one of the things I was hoping to rely on was your Editor control. Your previous versions created XHTML /WCAG compliant code and allowed for a customised interface for the users. I was hoping that moving forward our company would be able to implement better crafted HTML to the users browser. I was hoping for something 100% feature for feature with your other shipping editors.

Please look at creating a full blown editor for MOSS 2007. This really feels like a step backwards. I also hope that Micrososft have not bought you off from creating this better component through the agreement.

[edit]
Oops disregard all above, I should have read the entire thread before venting...

This is good news that you are also going to release a full blown editor.

answered on 01 Jun 2007, 02:21 PM

DownloadEditorMOSS.jpg

Hi guys,

First of all, on the behalf of the Telerik team, I would like to apologize for the long delay. Due to some last-minute changes, we've had to postpone the release and to ensure that everything will work as expected with the final version. We hope that you will like what the Premium version has to offer and that the wait was worth it.

The Premium version of RadEditor MOSS Edition is available for download in your Client.net account. For convenience I have attached a screenshot of the download location to this thread.

Best wishes,
Georgi Tunev
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

answered on 02 Jun 2007, 01:22 PM

Hi,
Thanks for the release.

I want to point out that for wss 3.0 ,in default installation, the hyperlink manager does not work as it requires MOSS 2007. I had to update the tools.xml file. In fact I was rather upset for the lack of this feature.

I like to ask for the price. We have purchased the radcontrols license, I guess that we can use radeditor for Moss freely.

The second thing is in documentation you mention about some Lite version and premium version, and I feel a bit of lost about it. Are there two versions of the Radeditor for Moss?

Lastly the editor works nicely with IE for list items, thumbs up for that.

answered on 03 Jun 2007, 12:47 PM

Hi,

As you already found out, the Hyperlink manager and the Reusable Content picker dialogs will not work in a WSS v3 site. These dialogs are part of the MOSS installation (they are using the MOSS Asset Picker) and are not included in WSS. Since our editor is primarily an MOSS product, we have included these tools in the default tools file. For a WSS site, you will need to edit the editor tools file and use the built-in editor dialogs ("HyperlinkManager" and "TemplateManager" without the "MOSS" prefix). These built-in dialogs will work fine in WSS, however they will not offer the same experience as the MOSS Asset Picker.

There are indeed two versions of the RadEditor for MOSS - a "Lite" version (the free version, which was available originally and still remains free) and a "Regular" version. The Regular editor does not have any limitations - all tools are available for use and you can also reuse the editor in your own custom web parts, pages etc. The Regular MOSS editor is included in the license for our ASP.NET editor. This means that if you have purchased a ASP.NET RadEditor license or a RadControls for ASP.NET license, you get the full MOSS editor for free.

Best wishes,
Lini
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

answered on 01 Apr 2008, 08:38 PM

hi, just wanted to ask for clarification regarding a previous reply:

"IE support
In the next update of the free MOSS editor (next month) we will provide the option to edit SharePoint lists with r.a.d.editor in IE as well. Microsoft has agreed that we can provide a setting which enables r.a.d.editor on IE as long as the default behavior is kept as it is now (r.a.d.editor is enabled only on non-IE browsers and Microsoft editor is enabled in IE)"

...does this mean that

a. the rad editor will work in IE for MOSS list items now as well?
b. the rad editor will work in IE for MOSS, but still excluding list items like the previous version?
c. the rad editor will work for MOSS list items as long as the browser is not IE?

if (a), which version of the rad editor was this released to? or am i on the completely wrong thread? i'm using rad editor 4.4.0 for MOSS and had activated the 2 features that should have made the rad editor toolbars work for list items, but it doesn't seem to work, and i'm using IE, and sort of getting confused now..

i'd appreciate any help. thanks.

answered on 02 Apr 2008, 07:53 AM

Hi,

When you activate both editor features, then RadEditor will replace the default list editor in all browsers. If you still see the original editor or a simple textbox, then you need check the following:

1. After you activate the features for the first time after the editor solution is deployed, you need to recycle the SharePoint web application. Do an "iisreset" and see if that fixes the problem.

2. The first time you activate the features, you need to be logged in with an administrator account. If you are logged in with a less privileged account, the editor features might not be activated correctly.

3. The editor features need to be activated for each individual site in a site collection. For example, if you have activated them in the root site, the editor will not show up in child sites until you activate the features there as well. Take a look at the following article, if you want to activate the features for all sites in a site collection - http://www.telerik.com/help/radeditormoss/Change_the_RadEditor_features_scope.html

Sincerely yours,
Lini
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

Product Bundles

DevCraft

Web

Mobile

Document Management

Desktop

Reporting & Mocking

Automated Testing

CMS

UI/UX Tools

Debugging

Free Tools

Support and Learning

Productivity and Design Tools

Important Info

39 Answers, 1 is accepted