Preventing editors approving their own content using Episerver approval sequences

Episerver approval sequences are a great way of controlling how editors get their content signed off by visually defining a set of approval steps that content must go through before it’s considered approved. In organisations that have compliance requirements a common requirement is that editors should not be able to publish their own content. This has already been covered here: Adding custom logic to your publishing step.

Continue reading

Tags: Episerver 10 Oct 06, 2017

Creating a "submitted form" KPI for Episerver A/B testing

“Episerver Often for non-commerce sites getting forms filled in and submitted is one of the most common goals of a site, usually for lead generation or to collect some other kind of user information that can be used by the organisation such as newsletter sign ups. In order to get people to fill in on-site forms editors should be able to experiment with their content to try and encourage users to fill in forms on their site(s). To help with this Episerver has built in A/B testing capabilities to allow users to experiment with different content versions measured against a KPI that’s the desired outcome. However there is no default KPI to check if a user submits a form.

Continue reading

Tags: Episerver Forms A/B testing Episerver 10 Sep 04, 2017

Hiding required properties on the create new page in Episerver

By default Episerver will show all required properties on the create new screen. I guess that it's presumed that the content cannot be created without these properties existing which in many cases is true (e.g. setting a list root). However in many cases I've seen the [Required] attribute used where the content could be created/edited without the property existing but we need to stop the content being published without it (see my note on using IValidator's later in this post).

Continue reading

Tags: Episerver Episerver Edit Mode Jul 27, 2017

Customising best bet behaviour in Episerver Find

This post describes how it's possible to customise how best bets behave in Episerver Find. It uses an example of matching best bets for specific Episerver locales.

By default Episerver only allows editors to define best bets for site(s) and/or language(s) defined for your site. This works well in most cases, however in scenarios where a site is set up to serve different countries using localisation of the same language it may not work as expected.

Continue reading

Tags: Episerver 10 Episerver Find Jul 16, 2017

Search

Episerver Nuget Feed Explorer

Tool to explore the packages available on the Episerver Nuget Feed:

    Go    

About me

I'm a former Episerver Most Valued Professional (EMVP). Now working for @Episerver as Director of Solution Architecture.

Recent comments

More Comments >>