With extensive updates to the documentation, some small code fixes and improvements, the 2.0.0 version of NitroNet introduces also a brand-new feature called Additional Arguments which allows to be more flexible and more compatible with the handlebars templates created with Nitro by the friendly frontend engineer of your choice. Weiterlesen
SUGCON EU, the Sitecore User Group Conference, is a yearly event located in different cities around Europe. Beginning April 2019, SUGCON was coming to London for 1 1/2 days. Packed with lots of sessions for all hot Sitecore topics, it … Weiterlesen
SXA contains the Toolbox feature, which provides Authors the possibility to drag and drop several components in order to add it to pages in the Experience Editor. You can also create a custom component and use it in the Toolbox like … Weiterlesen
Das 12. Treffen der Sitecore Usergroup Deutschland (SUGDE) seit deren Gründung in 2015 fand in der gut ausgewählten Location „Design Offices Nürnberg“ statt, welches unmittelbar nahe dem Hauptbahnhof und der schönen Altstadt liegt. Schon am Abend davor berichteten Jana und … Weiterlesen
Sitecore 9 introduced the dynamic placeholder feature. Please follow the official documentation for more information about when and how to use it.
The problem with the default dynamic placeholders
At first glance, the new dynamic placeholders look very straightforward. Basically, we provide an integer which is the amount of placeholders that should be rendered. Additionally, we can define the seed which indicates the starting value that is used for key generation (see example below). Also the markup customization possibilities are quite nice. However, when I used it in a project I ran into a problem that made me realize that the simple mechanism comes with a huge downside.
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.