Episerver pagetree search shows encoded html entities after upgrading to the new UI

Episerver first released their new refreshed editor ui with version 11.21.0 of Episerver.CMS.UI in June. Due to unintended semantic breaking changes this was (pretty silently) removed from the public nuget feed after a few days.

Weeks, and months, has passed. The refreshed ui has been released (again) and after numerous bug fixes, I finally agreed to update the website for a customer eager to try the new stuff.

Read more →

DropDownList in on-page editing?

The attributes [SelectOne] and [SelectMany] can be used in combination with a SelectionFactory to create Episerver properties in the form of DropDownLists and CheckBoxLists. This was introduced in Episerver 7.5, five years ago, and should be familiar to most Episerver developers. But, some editors are afraid of «All properties view» and would like to do all their editing in «On-page editing», what about them? They need a little extra work.
Read more →

Change text in the Episerver UI

Sometimes the names and texts in the Episerver UI can be confusing for the editors of a specific site. Luckily, we as developers can override all texts stored in Episervers language files, in two easy steps.

  1. Locate the text you want to override
  2. Add your own translation to an XML file

Read more →

Customizing the Episerver page tree

A website has content in a lot of different languages, some of the language codes are kind of cryptic looking and the editors don’t recognize all of them. When they view the page tree in a specific language, pages that does not exist in that language are shown in a gray font and the language code of the page’s master language are shown. The editors wants to see the name of the language, rather than the language code.
Read more →

Property prompt for Episerver

Today I discovered a feature I have never noticed before! You can add a placeholder, watermark, or (as Episerver calls it) a prompt to some properties.

[Display(Name = "String", Prompt = "Insert string...")]
public virtual string StringPrompt { get; set; }

[Display(Name = "DateTime", Prompt = "Insert DateTime...")]
public virtual DateTime DateTimePrompt { get; set; }

[Display(Name = "Int", Prompt = "Insert integer...")]
public virtual int IntPrompt { get; set; }

The prompt displays like this:

There is no point in repeating the name (label) of the property as the prompt, but describing the expected format (or validation) of the property, could be useful in some scenarios.
Read more →

Episerver help texts, improved

Life as a web editor can be difficult. Some larger Episerver solutions may have more than 100 different page types, each of which has many tabs with tens of properties. Each property has a label, which is a short text that tells editors what the property are for, for example «Headline», «Main Image» or similar.

Sometimes, the label does not have room for all the information that editors should be presented with, and therefore, Episerver has added the option to display a tooltip, an additional description that appears at mouseover on the label. There are a couple of drawbacks to this solution. There is no visual marking that informs the editors of which properties have such tooltip text and which ones do not have. And since often very few properties have tooltip texts, it’s quite likely that the editors don’t see the ones that are added.

If Episerver can’t fix this for the better of their ediors, other developers will find ways.
Read more →