On one of our current project we have a close deadline, therefore we need to simplify implementation and cut from the scope as much as possible to roll out the MVP with the full functionality but without Experience Editor support – as it’s not priority for now. We had a long discussion about this, the main reason of cutting scope is to keep the frontend simple as possible and focus on business logic functionality instead of editing experience. Therefore on the Sitecore side we are providing a few APIs for the frontend and not creating any layout, rendering and placeholders; only pure templates and content.Continue reading “Sitecore Headless – How to reuse Layout Service serialization in custom API Controllers”
Long time no posts about Sitecore Content Editor, but recently I got the following requirement on a project:
Continue reading “Sitecore default Save command post action usage”
Creating a new Save button in Content Editor to perform synchronization – with other items in the tree – of specific fields on the selected item.
Sitecore provides you the possibility to implement your own layout resolver if the default one is not enough for you. Basically you can change the layout of a page based on a business logic without changing the item in the database.Continue reading “Custom layout resolver”
The default Sitecore Name Value List field has an annoying issue. It does not allow to use special characters like ‘-‘ for the key. I just digged into the Sitecore.Kernel library and I found a regular expression validation which is hardcoded.
Let’s overwrite this class make it more flexible. The main issue with the implementation that they don’t encode/decode the URI.Continue reading “Sitecore Name Value List field with special characters”
The module is developed by @maaakstiles and I really like it because it’s easy to extend/change to fit your requirements. The basic idea is very easy. It gets data from somewhere (Sitecore/CSV/SQL/MySQL). I played with the SQL part.
I couldn’t find any documentation on the internet about this so here is how you can change the frequency of checking the scheduled task.
As you can see here in the config file you can do it separately for “core” and “master” database. On dev machines always needed to change it from the default 10 minutes to lower, e.g. 1 minute.
It was a good idea from one of our client to show a highlight directly on the renderings which use any Personalization Rules in Experience Editor.
I found out to create a HTML extension method for it and then I can include it to renderings. Then I can call it like this: