Sitecore

I believe that everyone, who installed Sitecore Azure PaaS had their silent question moment: “Where are all my logs, and how I suppose to monitor this?”. While the first question was answered multiple times (e.g. on StackOverflow), the second part is a bit more complex. You might think about what complexity I’m talking about? Yeah, putting Application insight Key is a no-brainer but it is far from enough to get observability of your system....

Some time ago we faced an issue with NodeJS slowing JSS in integrated mode significantly over time in Azure PaaS. We saw requests growing from sub-second to 3-4 seconds. Here is what you need to check as you do troubleshooting of your solution. Configurations & Checks Pass custom parameters to Node JS in integrated mode First of all, we tried to gather some information about NodeJS. To do that, we followed a recommendation by Adam, which you can find here: https://sitecore....

As you know GraphQL requires the schema to execute your queries. In Sitecore implementation, the schema is regenerated every time you touch templates. What we recently discovered, that if you have separate CD and CM, schema on the CD node will not be refreshed after publish. Luckily, this is quite easy to fix. You need to create an event handler and subscribe to *publish:end:remote *event. public class TemplateUpdateHandler : Sitecore.Services.GraphQL.Content.EventHandlers.TemplateUpdateHandler { public TemplateUpdateHandler(IGraphQLEndpointManager endpointManager) : base(endpointManager) { }`` public void OnPublishEndRemote(object sender, EventArgs e) { base....

It was quite common for Sitecore MVC implementation to add logic around renderings that will catch unexpected exceptions in them and save your page from complete collapse. Such logic hides your component from end-users and might only put something in HTML comments, while during preview or editing experience it will give some visual indication of an error and its details. Such functionality can also be very useful for React JSS applications, but it is not that simple especially for isomorphic apps leveraging SSR (server-side rendering)....

if you generating SCWDP packages for Sitecore you might get stuck at some point with a page saying *“Stay Tuned. We are updating…” *after deployment. This is what it means… Why The page is generated by a Sitecore utility called bootloader (Sitecore.Cloud.Integration.Bootload), which is a part of Azure Toolkit. This utility is responsible for the installation of other modules and the execution of post-build steps like configuration transforms. The content of a page is coming from the App_Offline file, which is place at the root of your web app and prevents requests from hitting any login in it....

This investigation of Sitecore JSS and SXA was done quite a while ago, but I didn’t get a chance to post it here. I need to go back to the validation of this setup so this will be a living post and I’ll be updating as new findings arrive. You might ask why would you need to mix them, but the reason is pretty simple. SXA brings a lot of functionality outside of presentation configuration (which I’m not a fan of) that can be useful for any site, like site management, wizards for site creation, local data sources, various site settings, etc....

It’s been a few months since I’ve published Packertemplates for Sitecore. Their main purpose is to create Virtual Box images with a fully configured Sitecore instance. So far I have both updates for Sitecore 9.0 CMS and Sitecore Commerce 9.0.1 scripted there. Recently one of my colleagues was tasked with the configuration of a standalone commerce server in a private cloud. ARM templates weren’t really useful there and we are too lazy to install everything manually....

It was not long ago when you need to mention Docker at least once during your presentation to make it cool and trendy. And actually, there is a good reason for that. Containerization provides a way to make environments portable and immutable. Immutable infrastructure for Sitecore would be much desired, but containers are on Windows are not so cool yet. It doesn’t mean that you cannot get it but we will need to bake it a bit differently....

It’s been a while since I wrote about Sitecore, React and embedded JS Engine. Also, my presentation on Philadelphia SUG last year was mainly theoretical. So the last few days I’ve spent cleaning up my sources that I’ve been using for those posts. It looks like that this time to open sources. GitHub https://github.com/asmagin/sitecore-js-presentation In the repo, I’ve put sources, samples, and some docs that I will update and enrich going forward....

If you are following ReactJS.NET topic, then you probably know that they are migrated to a new JS engine. Now the project is using JavaScript Engine Switcher, which supports multiple engines: MSIE, V8, Jint, Jurassic, Chakra Core & Vroom. As I’m planning to use JS engine to render components we need to know which one is the best. Test Setup For the test, I’m not going to use everything in ReactJS....

I’ve ended my previous post I’ve mentioned that I would add redux in a Sitecore-ReactJS mix. That is what I’m going to talk about in this post. An original solution helps us to reuse ReactJS views on the server which actually could save us time in development and maintenance. It was more about static content generation. While most of the sites I’m working with requiring more than that. Take an e-commerce storefront, a travel site, or utility customer portals, a customer would demand a lot of interactivity in all of them....

There were a few posts on the internet on how to integrate front-end code into a Sitecore solution. It all started with a post from Alex Shyba. Back in February, he describes the general concept of an integration. Then Richard Seal created a module for Sitecore that allow you to use jsx renderings in Sitecore. I was trying to solve a problem of an HTML handover between front-end and Sitecore developers for a while....

Our port of Sitecore Reference Storefront finally passed all internal checks and got open sourced on EPAM’s GitHub account right before Sitecore SYM 2016. Habitat version of a Sitecore Reference Storefront on GitHub Fell free to dig in and answer your questions in comments, social networks, or in person during the Symposium (you will be able to find near an EPAM booth during breaks) THANKS I would like to thanks my team in Kharkiv, Ukraine that helps me to make this project happen....

Context As I’ve mentioned in the previous post, I’m this one is going to be dedicated to one of the features. I think that it makes sense to start from a catalog, as an e-commerce implementation will heavily rely on product information all over the site. Let’s dive into … Implementation Catalog feature in our case covered most of the components on the site where you might see products, not including check-out: product recommendations on a home page, product listing component, product details page, etc....

I’ve been working a lot on Sitecore development infrastructure recently and package management is one of the areas, particularly NuGet. Unfortunately, Sitecore doesn’t provide any feed that you could use right away. so carrying over Sitecore DLLs in a repository is a standard practice that I’ve seen for few years and have actually been using. So I decided to create my packages and here how I did it. Versioning My goal was to create versioned packages for every version starting from 8....