I got a requirement that I need to create more data templates with the same fields but the fields should have different validations based on the template. So I decided to create a base template and inherit the other templates from this. Now, how can I assign different validators for the fields based on the template?
Continue reading “Template dependent field validator with Sitecore Rules Engine”
Today I created a rendering component which has around 10 fields but the whole component is not editable in Experience Editor. I decided to use Edit Frame from Glass Mapper. The BeginEditFrame wants all the editable fields as a parameter. But for around 10 fields not that comfortable.
The following code snippet creates an Edit Frame only with 1 field.
Continue reading “Glass Mapper – Edit Frame for all fields dynamically”
I faced the issue above when I upgraded from Sitecore 8.1 update 3 to Sitecore 8.2 update 1.
The question came up and wrote it to Sitecore StackExchange. Thank you @jammykam for your answer.
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.
Continue reading “Sitecore Data Importer – Media import from SQL”
When you would like to use your own custom template for images then you also need to do some changes in the “core” database to show those images which use your custom image template in “Select Media” dialog.
Continue reading “Use Custom Media template in SelectMediaDialog”
I just faced with the issue yesterday that I created my own search configuration to store only one field value in the index. I thought that it’s enough if I only index that one field what I want, but NOT.
Continue reading “Duplicated entries in Lucene index after item publish/save”
