Enable PowerPaste to Sitecore Rich Text Editor

By
In this blog post I will show how you can change Rich Text to behave similar like the TinyMCE PowerPaste plugin.

Changing the behaviour of paste 

When an editor is pasting text in the rich text editor, we can control how much formatting is removed.
In this example I have set the Paste to remove everything except newlines.
This setup could help content editors to easier move text from work documents(or other 3rd party tools) over to Sitecore without needing to use one of the paste buttons.

Changes needed to apply "Power Paste"

In the file:~/sitecore/shell/Controls/Rich Text Editor/EditorPage.aspx there is an EditorUpdatePanel with the setting StripFormattingOptions and StripFormattingOnPaste.
The original values are set to "MSWordRemoveAll,ConvertWordLists".
If we change this to
StripFormattingOptions="AllExceptNewLines"
StripFormattingOnPaste="AllExceptNewLines"
we would have the "Power Paste" activated.

Other options to consider if you want to strip less or more

  • NoneSupressCleanMessage: Doesn't strip anything on paste and does not prompt user whether MS formatting should be cleaned.
  • None: If no MS Word formatting is detected, content is pasted as is. If MS Word formatting exists, user is prompted to clean it.
  • MSWord: strips Word-specific tags, preserving fonts and text sizes.
  • MSWordNoMargins: strips Word-specific tags and margins, preserving fonts and text sizes.
  • MSWordNoFonts: strips Word-specific tags, preserving text sizes.
  • MSWordRemoveAll: strips Word-specific tags, fonts and text sizes.
  • Css: strips CSS styles.
  • Font: strips Font tags.
  • Span: strips Span tags.
  • ConvertWordLists: converts Word ordered/unordered lists to HTML tags.
  • AllExceptNewLines: Clears all tags except "<br />" and new lines (\n).
  • All: strips all HTML formatting and pastes plain text.


Comments

Unknown said…
Awesome tutorial. You have explained everything very clearly. It is really surprising to convert a normal Rich Text and behave it similar to the TinyMCE PowerPaste plugin.
I always use TinyMCE for website content creation because it supports various plugins and has a wide range of useful features. For Copy/paste task I prefer PasteitCleaned because it is completely similar to PowerPaste plugin but has much less monthly cost.
April 17, 2020 at 9:41 PM
manish said…
This comment has been removed by a blog administrator.
October 2, 2020 at 3:50 AM
Post a Comment

Popular posts from this blog

Step by step guide to add Glass Mapper to Helix solution

By
Image
How to add Glass Mapper to Sitecore Helix solution There are probably different ways to set this up in a Helix solution. I have done this setup in 4 of our projects, and it has become the "template" for our new Helix solutions. We create one foundation project, which has all the glass nuget packages installed, we also choose to add a glass base in the foundation layer. All new features will have access to this glass base interface through a project reference.  I have had a lot of discussions with my co workers on where to add common fields that would be used in several feature projects. If it should be in the Glass Mapper foundation project or in a new foundation project. On "small" projects we choose to add it in the Glass Mapper foundation project, on larger projects we created a separate foundation project to add these fields and their interfaces with Glass Mapper mapping. 1. Create the Visual studio project From the Package Manager Console run
Read more

Using interfaces with Glass Mapper

By
Image
In one of my previous blog post I wrote an example on how to add Glass Mapper to Helix . I will in this blog post provide some code examples on how to map different fields with Glass Mapper. I will also provide some examples on how you could benefit more from Glass Mapper by using interfaces instead of models. Why use interfaces instead of models Interfaces can be inherited multiple times, this works well with inherited templates in Sitecore. We create the common fields in the Helix Foundation layer, and use the mappings in multiple feature projects. The mapping is created in separate interfaces. The model(interface) that should use the fields only needs to inherit from these interfaces. For example a simple component with Title and Rich Text would only need to inherit from the GlassBase, Title and Rich Text interface IMyComponent   :   IGlassBase ,   ITitle ,   IRichText Inside Sitecore the MyComponent would need the Title and RichText field The view then has access
Read more

Adding dynamic image source for multi-site solutions with $site$ token and setting dynamic datasource location for components

By
Image
Months after finishing a project I have had clients saying: We need to make a copy of the site you created and put some other content on it Most clients need to put this new site into the same solution because of restrictions in their Sitecore license. To convert old projects there was usually a lot of content restructuring and code changes needed. I have done this exercise multiple times. I try to have this in mind when creating new solutions so we don`t end up with too much effort when adding support for multi sites at a later stage. Even with great structure and code we still face some problems. In a multi-site solution you want to reuse components, but the sites should not always share the data locations and image folders. Most sites have different editors, they should not see the components and images from the other sites, we then need to place content in different folders and set the appropriate security on those. I recently got a request to duplicate an existing site,
Read more