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 →

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 →

Episerver remote UDP events after upgrading to CMS 11

After upgrading a site from CMS 10 to CMS 11, this error surfaced:

Server Error in ‘/’ Application.

Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: The type ‘Microsoft.ServiceModel.Samples.UdpTransportElement, EPiServer.Events’ registered for extension ‘udpTransportCustom’ could not be loaded.

Source Error:

Line 55:   <binding name="RemoteEventsBinding">
Line 56:     <binaryMessageEncoding />
Line 57:       <udpTransportCustom 
Line 58: </binding> Line 59: </customBinding>

Source File: C:\Alloy\web.config    Line: 57

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.7.2633.0

Let’s figure out what’s wrong!
Read more →

Episerver.Forms and the solving of a performance issue

Forms are a key element of many websites to collect information and interact with visitors. Some examples of such forms are Contact us, Sign up for our newsletter and Apply for a job.

The block-based approach Episerver.Forms makes assembling a new form a familiar experience for Episerver-editors. Complex forms require a large number of blocks, and thus a large amount of clicking, typing and publishing. Even though the experience is familiar, creating a form is not necessarily a five-minute task.

A small form with two-three text-inputs, a few radio buttons and a submit button are quick to set up and works flawless. Real life use cases are not always quick and flawless. When a customer created a quite large form, with five text fields, 70 groups of radio buttons and a total of 35 headings, the page containing the form took 25 seconds to load. Not so quick and flawless anymore.
Read more →