If you have a custom SOLR index in your Sitecore-based project and it becomes too big (more than 1 million documents), you may face a problem when the rebuild process times out because of the SOLR connection timeout exception. Today, I’ll tell you how we dealt with this issue.
In this blog post, I will tell you how we built a custom Sitecore JSS Snippet component in a project based on Sitecore 9.2 SXA + JSS and explain how it helped solve a client’s requirement.
All members of the Sitecore community must have heard by now of the Sitecore 10 release announced in August 2020.
In this article, I’ll discuss the most prominent improvements and new official features that come with this release and explain the benefits these bring to developers, marketing specialists and customers.
In this blog post, I will describe an issue we had in a project that was based on Sitecore 9.2 SXA + JSS, and explain how we solved the problem.
Sometimes, we need to import Sitecore content data in the scope of migration or deploying process. In general, we can use Sitecore Migrations tools (if we need full migration). But if we just need to export content data, we can use Sitecore Package Designer, Unicorn or TDS.
In my case, we needed to migrate dozens of content items (more than 40 000) from Sitecore 7.5 to Sitecore 8.2. And we had only Sitecore Package Designer.
The main issue we faced was the long processing time (a couple of hours) of Sitecore Package Designer. This was the trigger for us to release our Sitecore Data Transfer tool.
Today, I will not tell you about all the new features in Sitecore 9.2 but would like to draw your attention to the serialization mechanism.
For modern businesses, it’s extremely important to be flexible in order to satisfy the constantly changing customer needs. That’s why more and more companies turn to the evolving cloud computing services, which provide scalability, optimize connectivity and improve performance.
Sitecore is not an exception, as it allows you to deploy solutions on the Azure Platform as a Service (PaaS). For a new Sitecore environment, you can use out-of-the-box web deploy packages (WDP). But to deploy your existing (local) solution, you need to initially package it into a WDP.
In this article, I will tell you how you can package your local Sitecore Habitat into web deploy package (WDP). You will also see what issues you might run into during the process.