This is a quick tip if you want to set the log of SOLR to ERROR. It is useful in production environment where you don’t want to collect all data every time and avoid filling hard drives with log files.
Author: davecoding
404 and 500 Error Pages – Part 2
In the previous post we saw how to create the Sitecore items needed to handle a page for 404 and another for 500 errors, as well as the necessary changes in some config files. Now, we will look at some changes in code to display the correct HTML code.
Let’s start by creating a new rendering in Sitecore. I first created a new Rendering Folder called “Test”, but that’s up to you (/sitecore/layout/Renderings/Test):
404 and 500 Error Pages – Part 1
In this post I pretend to share only one way to do friendly error page (500) and not found (404) page in Sitecore. I say one way because this is just one way to do this since you might find another that suits best your needs. This first part includes Sitecore items and config changes. Last but no least, I am using a version 8.1 update 2.
To begin, let’s create a template for the error pages that can be as complex as you need, but here is just an example with one field for the error code:
Drop downs values pulled from EpiServer
I am pretty new in EpiServer, but here is my attempt to fill some drop down lists with data coming from the CMS. I am using a version 6 of EpiServer since this is the one I needed to work on when I made these changes.
I had a form with some drop down lists which its content was hard-coded. I was asked to pull the data from the CMS:
Sitecore Hackathon 2018
I participated in the Sitecore Hackathon the last February. Overall, the experience was great, but here are some comments and notes if you want to participate in coming ones.
First, it was my first hackathon. Yeah, sounds weird.. but really I haven’t participated in one before. I have, however, participated in a couple of programming competitions. I even won one of them when I was in college 😎.


