The situation One of our clients reported recently, that the content managers started to be affected by a situation, where they were… not able to fully load the Sitecore Experience Editor anymore (stuck with the spinning loading-icon) and also weren’t … Weiterlesen
Sometimes it can be necessary to set certain HTTP headers to increase the security of your Sitecore site. Many customers of us have requested such a feature and therefore we implemented this functionality where a site admin can set various HTTP headers … Weiterlesen
If you found all your way to this article, chances are you ran into the following error during installation of Sitecore 9.0: „Cannot bind argument to parameter ‚Signer‘ because it is null.“
Sitecore provides many ways to integrate own logic while executing specific actions. One of those ways is event handler.
1. Default Event Handler
Sitecore have per default some events which are defined in Sitecore.config configuration file.
This blog post is based on the Article Add Export to File Functionality in Sitecore’s Search Options by Dean Mark Soriano.
To follow this guidance as well as possible it is required that you have already completed the steps from this blog post:
Now we want to export the result list into an excel file.
Visual Studio plugins and extensions are kind of tools which could make our work easier and much more efficient. With the VSIX Project Templates in Visual Studio SDK, we are able to extend the functionality of Visual Studio and to create own features. Every developer using Visual Studio could implement tools according to his needs.
Many of you know this problem: We have a bucket containing items and we want to visualize the items in a list with all values and not only the standard properties like:
The magic words to do this, is „Dynamic Placeholder“!
First of all some words about Sitecore and Upgrades
When I was a beginner in Sitecore developement, the Sitecore world stands almost still for several months to years with the release of Sitecore 6.5.
So what I want to say with that is the product was more or less very stable with few small issues and no big need to update the solution for business or technical reasons.
What we did was creating wonderfull solutions without thinking to much about „how we will update/upgrade this in the future“. In my opinion Sitecore haven’t done the same in that dimension they have to do it now.
Often a Sitecore infrastructure consists of a single server instance with two – maybe three – environments (development and production) which was easy to maintain and handle.
Years go along management environements separate from delivery machines more and more, single server instances disappear in many cases to high scalable solutions with multiple servers for webapplications, sql servers, mongodb instances. Publishing instances and third party products not included.
On the other hand, we all get a little bit older: the employees searched for new challenges in other companies and you remember them only from some years ago.