Welcome to this blog

By
When I first started as a Sitecore developer, it was hard to find solutions to Sitecore related problems with Google. This has changed, now there are several great blog posts out there that points me in the right direction. I hope my blog can point some of you in the right direction to your problems.

About me
My name is Ole Kristian Hvaale.
I live in a small city Kongsberg (Norway).
I have created web sites, portals and eCommerce solutions since 2007.
The first years I worked mostly with Umbraco and similar CMS systems.
In the later years I have been working as a team lead/tech lead in Sitecore projects.

Comments

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

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 opti
Read more