Version 1.1 of RadEditor for MOSS
Sharepoint 2007 in french
31 Answers, 1 is accepted
Currently, all flash and media content is stripped by the MOSS content filters after you submit it. Unfortunately, this happens on the server and we have no control over it. We are currently investigating ways to skip the filters.
Regards,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
We're experiencing the same behaviour as reported by Manon Girard (the OP) - both with the standard Rich Html Field Control and the Telerik equivalent. We're importing content from a legacy CMS with embedded Flash (i.e. object tags) and JavaScript - both are stripped from the content upon saving the page.
However, we've discovered that content - when assigned using the WSS API (i.e. Page["field"].Value = "<object />") apparently doesn't strip the content.
If in fact the Telerik team is right (about the content filters), then there's no way around this. Even a custom developed Field Control would suffer this behaviour (even the simplest plain text Field Control) - the <object /> tag would get stripped unless Field Control would encode / decode the <object /> tags upon saving and loading the content. However, I find it troublesome that the MOSS team implemented this without knowing about general customer requirements (or else they simply ignored it for sake of "security").
We've got a long track record with many CMS systems (largest Microsoft CMS vendor in Denmark), and find it really frustrating that this limitation has been built in to MOSS 2007. We've just been through a support case with Microsoft (level A - highest escallation level), and they state that this behaviour is by design.
As an architect, I think this is one of the worst design decisions I've ever seen (I would much rather use MCMS 2002 SP2 than MOSS 2007 given all the constraints for regular WCM). Thinking that no customer would ever want to embed Flash files directly inline with regular text content is definately not based on an understanding of customer needs.
Sure, you can create a WebPart zone and handle things from there with the standard content WebParts - however, this approach is 10 times more complicated for the customer (and you don't get versioning in WebPart zones), and completely defeats the purpose of WCM for regular users.
I'm hoping that Telerik is able to figure this out .. we're reaching a tight deadline and are facing serious delays because of this.
Any ideas?!
I can promise you that we will do our best to find an appropriate workaround, however I cannot tell you when exactly we will be able to do this. Generally speaking the main problem in this case is that we cannot control the presentation content everywhere.
We will need more time to research possible options and if we manage to find an appropriate solution, we will implement it right away.
Sincerely yours,
Georgi Tunev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Thanks for taking the time to discuss the problem on MOSS 2007 stripping certain elements from the HTML. We're pretty hard pressed on time with a big Danish customer and discovered in the last minute that imported content was missing some data.
We have a deadline coming up and would like to share our findings and ideas for a stable common solution.
Content Filter:
We've been talking about a "Content Filter" that is resposible for stripping the tags from the content value - before loading or saving from the backing datastore. What's really interesting is exactly when this "Content Filter" kicks in - is it before or after the FieldControl receives the content (for saving or loading).
My initial guess would be that content is filtered after the (Telerik) FieldControl has received content from the UI editor and forwarded it to the backing store. We've just verified that this behaviour also applies with other FieldTypes such as the "Multiple Lines of Text" FieldType (when associated with a Telerik FieldControl), so there's definately something going on ..
Bypassing the Filter:
In order to circumvent the "Content Filter", the invalid tags in the original content needs to be masked / encoded, so that the (again, speculation) regular expressions in the "Content Filter" is unable to find and eliminate our beloved tags (<object/> and <script />).
Ideally, one could simply identify the relevant tags and (BASE64) encode these before submitting them to the backing store. We thought about deriving a custom FieldControl from the default Telerik FieldControl and overriding the relevant methods and properties - implementing the masking / encoding algorithm.
Basically, the content of each of the special tags is encoded and embedded within an <xml/> attribute (or similar), that allows us to identify the type and value of the original tag. When saving, a set of regular expressions identify the tags and apply the encoding. When loading, a set of regular expressions perform the reverse operation - identify the tags and decode according to the "originalTagName" attribute in the <xml/> element.
Original Content:
<object>content</object>
<div>here's an Html fragment ..</div>
<script>content</script>
Encoded Content:
<xml originalTagName="object">BASE64 encoded content</xml>
<div>here's an Html fragment ..</div>
<xml originalTagName="script">BASE64 encoded content</xml>
I've pitched this idea against several other developers in our company and they think it's a pretty clean solution as it's a completely transparent operation as the content gets filtered whenever the WSS API loads / saves content (e.g. a custom Windows Service that loads the data will see the correct value).
The contents of this message was also sent (in a slightly different version) to Dimitri.
Just a small update for the current status of the product. The next editor for MOSS release is scheduled for July 4th. The publishing field and web part editors should be able to support Flash/Scripts in that release.
Greetings,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Great news. We're awaiting the next release and will dedicate our resources to other parts of the probject.
Please make sure you test with lots of different combinations of <object /> tags and inline Html (preceding and following the <object /> tags). The current version of RadEditor for MOSS (spontaneously) stripped Html following the <object /> tag.
I already reported this to Dimitre, but please make sure you're covering this case in your tests.
Thanks in advance.
We are really happy to learn this news. We will test the new version quickly. Thanks
It's 5th of July and I'm unable to find any updates. Are you prepping the release or do you need more time?
Thanks in advance
Anders Borum / ProActive
I am afraid that the update will not be available this week. Due to some last-minute problems we decided to postpone the release for several days and make sure that everything will work as expected.
The release should be out at the end of the next week - please excuse us for the delay.
Best wishes,
Georgi Tunev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Any updates on this release date? We're anxiously awaiting the feedback from your development team.
Thanks in advance.
Currently we are fixing some problems with the editor's configuration file. Once this is done we will release the new version. We apologize for the delay.
Best wishes,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
We've been waiting since friday (20th of july) for your promised beta release and haven't received any information on further delays or issues that may have kept you from releasing the beta.
We're only interested in the WCM part of the Telerik RadEditor (which has been resolved, according to telerik employees).
As you already know, we're extremely close to a deadline of a major client. As can be read from the entries in this thread, telerik gave no reason to assume that this problem couldn't be fixed.
In fact, you state that the only thing keeping you back was minor configuration issues (and that's almost two weeks ago now). I'm very dissapointed by the feedback on this issue which is affecting a very large client of ours ($10 bn. and more than 450.000 employees). We've held back our own development on this issue (and presented our thoughts to help in solving the problem), based on the positive feedback in this post (and phone conversation with your technical support).
We need information on your expected release (and please make a trustworth statement this time). You already have my contact details - please get in touch and deliver on your promise.
Thanks in advance.
I see that Lini has already sent you the new beta yesterday, for convenience I am pasting part of his reply below.
We would also like to apologize for the big delay. Unfortunately we've stumbled upon 2 major problems just before releasing the product on the promised date. To our regret we are still not able to find an appropriate solution to them but we are working on it. Once we have them fixed, we will upload the official release right away
Here is the change log for the current version as well as the known issues we need to take care of before the release:
Changes in version 4.20
- RadEditor updated to 7.13. Removed viewstate for the RadEditor control (it is created on each page load).
- code cleaning (web part + MOSS Tools client scripts, moved toolpart scripts into main scripts folder, removed EditorWebPart folder)
- new class MOSSRadEditor - base class for RadEditor in MOSS. This class should be used in custom MOSS solutions. Use the MOSSRadEditor.Content property to get/set the editor's html.
- no longer dependant on the form.js script (caused JS errors in some pages)
- fixed the asset picker script registration (caused problems with AssetUrlSelector controls)
- CssEditor.css file loaded in presentation mode for all editors
- Images, Documents, Flash, Media paths set from the Configuration file (if present)
- ConfigFile and ToolsFile properties for the WCM field
- removed unneeded title attributes from the tools files. Localization should only be set from the Main.xml file from the Localization folder.
- fixed localization strings for some tools (e.g. MOSSTemplateManager)
- added AllowSpecialTags property to the WCM field. If set to true, the user will be able to insert object and embed tags (Flash, Media content)
- added compatibility with the old SPS 2003 web part type. There is no more need to compile an additional assembly
- marked the Telerik.SharePoint.EditorTools.GetVirtualResourceFolder() function public. Now developers can use it to get the editor's RadControls folder location.
- spell checking now enabled for the Lite version as well
Known Issues
- Automatic update of reusable content is not possible at the moment
- inserting Flash/media in Firefox/Safari sometimes does not work
Sincerely yours,
Georgi Tunev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Here is my code. I have followed the instructions in the Deployment and Configuration Manual, but I'm not sure everything is correct for the new Beta Version.
<%@ Page language="C#" Inherits="Microsoft.SharePoint.Publishing.PublishingLayoutPage,Microsoft.SharePoint.Publishing,Version=12.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c" %> | |
<%@ Register Tagprefix="SharePoint" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%> | |
<%@ Register Tagprefix="WebPartPages" Namespace="Microsoft.SharePoint.WebPartPages" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%> | |
<%@ Register Tagprefix="PublishingWebControls" Namespace="Microsoft.SharePoint.Publishing.WebControls" Assembly="Microsoft.SharePoint.Publishing, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c"%> | |
<%@ Register Tagprefix="SharePointWebControls" Namespace="Microsoft.SharePoint.WebControls" Assembly="Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" %> | |
<%@ Register TagPrefix="radE" Namespace="Telerik.SharePoint.FieldEditor" Assembly="RadEditor.Net2, Version=7.1.3.0, Culture=neutral, PublicKeyToken=852c9eb6525c1b53" %> | |
<asp:Content ContentPlaceholderID="PlaceHolderPageTitle" runat="server"> | |
<SharePointWebControls:FieldValue id="PageTitle" FieldName="Title" runat="server"/> | |
</asp:Content> | |
<asp:Content ContentPlaceholderID="PlaceHolderMain" runat="server"> | |
<radE:RadHtmlField runat="server" id="Content" FieldName="pdefContent"> </radE:RadHtmlField> | |
</asp:Content> |
Thanks,
John
We have already released the MOSS RadEditor update. You can get it from your Client.Net account. Please follow the deployment instructions from the documentation file for deploying the editor in the WCM scenario.
Regards,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
We have not purchased the component yet, we just want to verify that it will work. Please send me a link to a trial version if it is available.
Thanks,
John
Version 4.31 is the latest available build. For the WCM field, you need to set the AllowSpecialTags property to true before you can insert flash and media. Here is how to do that:
- Open SharePoint Designer and navigate to the desired page
- Open the page and choose Edit Page Layout
- Click in the radE:RadHtmlField control so the TagProperties pane is updated with the control
- Set the AllowSpecialTags property to True
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
I have did the 4 steps mentioned above but the inserted flash still disappears after saving. However, the flash is shown when in edit mode. Am I missing something?
Alvin
Singapore
I assume that you are using the 4.31 (or later) version of the RadEditor for MOSS. If you are not, then please upgrade to the latest available release.
If you are using 4.31 or later, then you might have missed something in the WCM field setup. Check the MOSS editor documentation and make sure that you have set up the WCM field and set the AllowSpecialTags property using SharePoint designer.
Finally, if you still cannot get the field to save flash content, please send us the HTML from the editor (switch to HTML mode, select all content and paste it into a text file). We will check it on our local MOSS installation and tell you if there is a problem with it.
Best wishes,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
I found the missing step 5! We should "check in" the file after adding the tag! The flash shows up fine after that.
Alvin
Singapore
Thanks for the information. We will update the documentation to reflect this.
Regards,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
You cannot enter Media / Flash files in SharePoint forms scenario (Lists, Wikis, Blogs, etc.). There RadEditor does not have control over the presentation view which means that we cannot control the output when it is not in edit mode.
Greetings,
Georgi Tunev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Any ideas on ways to work around this?
I'm using WSS3, and probably don't have budget for MOSS2007 anytime real soon. My goal is to enable my documentation folks to put HTML versions of our assembly procedures online for our manufacturing group. Today this includes text and images, but someday will include video media as well.
Since I don't have WCM Scenario in WSS3, ideas?
Unfortunately, so far we have not been able to fix the content limitation problems in lists. I can only suggest that you create a solution using the RadEditor Web part. The web part has no content restrictions so it will display flash and media content.
Best wishes,
Lini
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Is there any advance on this issue?
Unfortunately, this is yet another problem, caused by the MOSS content filter. When you submit the page, MOSS will validate it and automatically make changes if the content is not valid. You can verify this by trying to enter the same content with the original SharePoint rich text editor.
We have not been able to find a workaround for this behavior yet.
Kind regards,
Stanimir
the Telerik team
Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
We are still not aware of a workaround for the rich content (flash, video) in lists in MOSS 2007. If you need to include such content, the only solution is to use a different scenario - either a content editor web part on your page or a WCM RadEditor field, which controls the presentation mode of the content and can go around the SharePoint content filters.
Regards,
Lini
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
What about Sharepoint Foundation 2010? - I tested it and I was not able to add <object> elements in SP2010 list or blog also.
Kind regards,
Stanimir
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.