This blog will show what do we need to add to the project so Glipmse could work with EPiServer.
This blogpost is meant to shed some light on the use-cases when EPiServer editors need to set Font Awesome icons.
By default, EPiServer encodes the text before setting the labels for SelectionEditor items. What I needed was to display some HTML in this text as well in order to show the font-awesome icon set editor can choose from.
Ever added a new property with a default value and were annoyed that it's null for already created pages?
We implemented the comments as blocks and saved them to the content area on the page. This gave us some problems with IChangeTrackable for the page.
We have been using the standard search solution in an AD authentication based Intranet. It did work locally, I swear! But, for some of the test users, it just behaved unpredictably.
FACT: VS extensions and copy paste rock when creating new EPiServer items. BUT: have we not written it 100 times, so why bother to click when we can type it in. This kind of thinking might just be wrong.
I've previously written about extending the link functionality to enable linking to the specific part of the page instead of top only. These are improvements for it.