Sitecore
Continuing with my series of blogs describing what each line in the Sitecore logs mean, today I want to talk about Caches and XML Configuration load. In this post, we are still examining the log file. In future posts, we will explore Client, Crawling, Eds, Exm, Fxm, Search, Publishing, Aggregation
Sitecore
Sitecore Forms comes with an out-of-the-box dropdown list field that allows you to choose between a static or a dynamic data source. In today’s blog post I am sharing a simple way to create a custom dropdown list that displays external data from systems such as Salesforce. The complete
Sitecore
The scope of this post is to walk you through a detailed process of how to create a custom Form element. You can achieve the same by following the Walkthrough: Creating a custom form element page. However, I want to share a step by step process with some extra explanations
Sitecore
I want to start a series of blogs describing what each line in the Sitecore logs mean. I am basing my research on the log information extracted from Sitecore 9.1 Update-1 with the log priority level set to “INFO”. Let’s start with the log file. The log file
Sitecore
Recently, I was working on a Sitecore implementation that has 3 publishing targets: “staging”, “web1”, “web2”. As the number of items in that site goes beyond the millions due to the number of languages and versions, we decided to install Sitecore Publishing Service. Among all the items, one specific page
Sitecore
Sitecore Forms enables you to easily create forms by dragging and dropping fields. It also supports Bootstrap. However, if you want to use Bootstrap framework, you must follow a set of steps to add the proper wrapper and classes around each field. Needless to say, this approach is not user
Sitecore
Recently, I had restored a “production” backup of the master and core databases from a Sitecore 9.0 Update-1 instance to my local SQL server installation. After that, the Sitecore log started filling up with the exception: Sitecore.XConnect.XdbSearchUnavailableException Message: The HTTP response was not successful: InternalServerError. Examining the
Sitecore
Recently, after pulling the latest changes from my team, my local Sitecore installation started showing every item duplicated. Not only the LaunchPad was behaving like that, but also the Content Editor. This issue only appeared in local Sitecore installation. Azure environments (DTAP) where not reproducing this issue. What was happening?
Sitecore
Recently, we had a requirement where we needed to personalize content based on the current host. The requested scenario was: visitor can access the same site from different hosts. For example: pension.company.nl, insurance.company.nl, mysafety.company.nl. Based on the current host, the visitor should see a
Most Valuable Professional (MVP)
João Neto Wins Sitecore “Most Valuable Professional” Award Elite distinction awarded for exceptional contributions to the Sitecore ecosystem Amsterdam, The Netherlands — January, 31, 2019 João Neto has been named a Most Valuable Professional (MVP) in the Technology by Sitecore®, the global leader in digital experience management software. João Neto was
Sitecore
I have been studying unit testing and investigating how I can use it on Sitecore projects. One good usage I discovered (despite all the extra work now I have to setup a unit test project) is writing a code that uses Sitecore API and I can actually trust. In this
Sitecore
As a developer, I tend to not pay too much attention to certain parts of Sitecore. Some of those parts are the functionalities available on the Experience Editor. Here I share four things I recently learned about the Experience Editor. I am currently taking the Sitecore® Web Experience Management eLearning.
Sitecore
Publishing Service enables you to schedule tasks through the task scheduler. It comes with the PublishTask and PublishJobCleanUpTask default tasks. The good news is that we can create custom scheduled tasks as well. In this post, we are going to create a scheduled publishing task which on a given Interval
Sitecore
Sitecore Publishing Service replaces the existing Sitecore publishing methods with a faster, reliable and user-friendly solution. It reduces the amount of time spent publishing large volumes of items and provides better visual feedback to the user. It was released for Sitecore 8.2 and is also available for Sitecore 9.
Sitecore
The Publishing Service is a module that replaces Sitecore publishing functionality. This module increases the speed for publishing large volumes of items and improves the user experience. As the Publishing Service runs on a separate process to the Sitecore CM instance, it contains its own logging file located at the
Sitecore
In this post I share a quick tip on how to to check if the current page is Forms Designer. Sitecore Forms comes with default form elements that you can easily drag and drop on your form. Those default form elements are divided into four categories: Basic, Lists, Security, and