So Sitecore 9 is out and with it quite a lot of new exciting features and functions. One is more awaited than the others. Sitecore Forms. In this blog post I will be taking a look into the forms in combination with the experience accelerator. Hopefully Sitecore has a new powerful tool that editors can use to create powerful forms with ease. Continue reading Let there be forms! Sitecore Forms!
I have not used SXA (Sitecore experience accelerator) a lot and I am not sure why. The fuzz has not been about SXA, but maybe there should be more fuzz about it. It is a handy tool for enabling the fast creation of sites. It should really be considered, at least when creating campaign sites or smaller solutions. Continue reading SXA and Sitecore 9 – Setting up a simple site
Many of today’s Sitecore implementations contain lots and lots of items. In many cases the items are stored in buckets and the editors are therefore totally dependent on finding what they are looking for by using the search functionality in Sitecore. When entering the search in Experience Editor the editors may become a bit overwhelmed with information since the default is to search for everything. Normally the editor could start filtering and then search for whatever is needed. Continue reading Customize default search in Sitecore experience editor
As the title says when an editor pastes text into a single-line field in the experience editor, the html formatting does not get stripped correctly. This bug has been verified in Sitecore 8.1 and 8.2. I have not tested in any other versions.
What I have done here is to change the field type in the home item of an empty Sitecore installation to a single-line field. I then searched for “Sitecore rules!” and copied+pasted the title from google into the single-line text field and saved the item.
There is a patch for this provided by Sitecore support. It can be downloaded here:
When applied the html stripping of formatting should work as intended.
The version of the patch says that it is built for Sitecore 8.2, but Sitecore support has told me that it will work fine for Sitecore 8.1 as well.
Sitecore’s media library does a good job of keeping the media that you want to use on your site, but the amount of media in a large site may become hard to navigate. The editors will then rely on search to find what they are looking for. Wouldn’t it be nice to be able to search for the contents of the images instead of the metadata? Continue reading Integrate Microsoft AI in Sitecore media library
In a lot of cases it would make sense to tell Sitecore at what time to execute scheduled tasks. If for example a heavy import job is to be executed once a week it would make sense to do it at a time when the editors are not active or when the traffic to the site is low. Continue reading Extending scheduled task to set execution time
This is part 2 of adding a second master database. When having a second database with the purpose of holding millions of items and not needing publish since it will contain information from third party systems such as DAM or PIM we need to stop the publisher from publishing the information that is linked in from the second master database. Continue reading Make Sitecore stop publishing certain items
In the official documentation you can read that Sitecore will choose index based on the RootPath in the crawler and based on the placing in the web.config.
Basically if you create an index that indexes everything under /sitecore/content/home/products you will need to get that index defined before for example the master index in the web.config otherwise your new index will not be considered at all. But what does actually happen here? Continue reading How does Sitecore ContentSearch determine which index to use
Have you ever wanted to add a second database so you can keep millions of items in it and not having to publish it?
Well, to be honest me neither until a few days ago. The scenario is that you have lots and lots of data in other systems (PIM, DAM, Pdf-library or whatever). You want this data to be accessible in Sitecore but you do not want to publish it since that will take forever and cause all sorts of problems.
So in this case you could keep all that data in the second master database (in a bucket of course, since the content tree will be quite hard to handle otherwise). Continue reading Adding a second master database