Sometimes you need to use a bucket in Sitecore to handle several items. This really depends on the specifications or needs you have, but a general rule is to use buckets when you plan to have several products, media files, etc. In case you need more information about buckets, you can visit the Sitecore documentation about it.
Continue reading “Custom Pipeline to Resolve Items In a Bucket”
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.
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):
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:
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:
Dave Coding 