Descriptive alt texts on images are important, but in TinyMCE the field is called «Image Description». You can change that!
Når egenskapene i Episerver blir for mange, kan det lett oppleves kaotisk. Jeg viser hvordan vi kan rydde og gruppere, så det blir enklere å finne frem.
After the introduction of TinyMCE editor v2, creating an initialization module is the recommended way of configuring TinyMCE in Episerver. This works well when you want the same configuration for all your XhtmlString properties, but that is not always the case.
Safely rename an Episerver property, and retain the value it had before it was renamed, using a migration step.
Until the release of EPiServer.CMS.Core 11.14.0 renaming a custom property was not that easy, now we can just add a GUID to our PropertyDefinitionTypePlugIn-attribute!
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!
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.
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!
In Episerver CMS, you are probably familiar with the concept of grouping properties into tabs. I show how you may move Episerver's built-in properties, and even tamper with the special tab PageHeader.
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!
Do not confuse your editors. If they do not use the property, the do not need to see it!
MediaData, the base class for files and images in Episerver, does not implement ILocalizable and thus does not have the option to include culture-specific properties. I present a workaround.
Editing image properties would be more intuitive if we could see both the image and the properties at the same time! Let's add image preview to All properties view!
The attributes [SelectOne] and [SelectMany] can be used in combination with a SelectionFactory to create Episerver properties in the form of DropDownLists and CheckBoxLists. Let's make them work in one-page edit!
You can add a placeholder, watermark, or (as Episerver calls it) a prompt to some properties. See how it's done!
Jeg sjekker ut de nye egenskapene til Episerver, ser hvordan de fungerer, og hvordan vi kan gjøre tilpasninger.