During Episerver’s great «Come back stronger» initiative that lasted from April 1st until the end of June 2020, I took a few e-learnings courses and convinced a couple of our customers to do the same.

I have never used Episerver Social Reach previously and did not have second thoughts when one of the customers wanted to try it out after completing the editor course where it was demonstrated as a useful tool.

According to the user guide Social Reach let you easily post to various social media like Twitter, Facebook and LinkedIn.

However, the only thing that works is posting to Twitter. I have been in contact with Episerver support and encouraged them to update the documentation, or at least add a warning that posting to LinkedIn and Facebook does not work. They did not listen to my suggestion.

I feel bad for trusting the documentation, installing Social Reach, spending both my own and my customer’s time, for really nothing but frustration and broken promises. There are better ways to post to Twitter than Social Reach!

Please, please, can you update the documentation?

Content types (like page types and block types) may be safely renamed, as long as you specify a GUID parameter in the ContentTypeAttribute of the class. The properties defined on a content type do not have the optional GUID parameter. If you simply rename a page property Episerver will just add another property to the same page.

To ensure that the existing property is renamed, and retain the value it had before it was renamed, you should use a migration step.
Read more →

Until CMS-14783 was completed in EPiServer.CMS.Core 11.14.0 a custom property was always identified by its TypeName, i.e. Alloy.Models.Properties.PropertyStringLst for the property definition below.
Read more →

Using UIHint you may choose if a string property should be displayed as a single-line or a multi-line editor. But why is the multi-line editor so wide, and the single-line editor so narrow? We can fix that!
Read more →

Using an EditorDescriptor, it is possible to add a property count to each tab in edit mode. Now, we can easily see how many properties that reside in each tab.
Read more →

Have you ever published a meaningless change to a Episerver page, just to make sure the Find index is up to date? Have you struggled with the Find UI to figure out what’s indexed for the page you just had opened in edit mode?
Read more →

Read more →

I’ve previously described how you can move built-in Episerver properties to a different tab. This will only work perfectly if the destination tab already contains another property for the same page. If not, the title will look strange, the sort order will be missing, etc. Today we will move a property to a non-existing tab!
Read more →

In Episerver CMS, you are probably familiar with the fundamental concept of grouping properties into tabs. You may place your own properties in the existing tabs (Content, Settings etc) or create your own tabs with descriptive names.

You may, however also tamper with the special tab PageHeader!
Read more →

Episerver has several built-in property types you may add to your content types, including DateTime that displays a date and time picker. Sometimes you do not want the time, only the Date!
Read more →