Sitecore Docs - Tech Tips by GS

If you are not already aware, Sitecore is moving its public feed from sitecore.myget.org to a different feed provider on November 30, 2023. The URL of the new public feed is: https://nuget.sitecore.com/resources/v3/index.json The URL for the internal artifact provider is: https://cloudsmith.io/~sitecore/repos/resources/groups/ The custom NPM feed will move from https://sitecore.myget.org/gallery/sc-npm-packages to the public NPM provider https://www.npmjs.com/ Both the original MyGet and the new public feeds are available now. After November 30, only the new NuGet and NPMJS public feeds will be available. Sitecore strongly recommends that all customers and partners update their CI/CD processes and build scripts to use the new public feeds as soon as possible to avoid interruptions beyond November 30, 2023. The above information is shared by Sitecore  here . How this can impact you? This can impact you if you are making use of these URLs. Such URLS are usually used in Build/Release ...

Is sxa_site cookie necessary for Sitecore website? If you are working on a requirement for cookie consent of your site, this question will definitely strike your mind. You would like to know that "sxa_site" cookie is not really necessary for Sitecore SXA websites. According to Sitecore support team, the website still works in case you remove the cookie. So, this is not one of the necessary cookies for cookie consent. Ever wondered what sets this cookie for Sitecore SXA sites? Following code in snapshot is used to set the cookie in Sitecore.XA.Foundation.Multisite.Pipelines.HttpRequest.StoreSiteNameInCookie processor- Even knowledge of such little things can be highly useful when handy at time. Hope you like it!!

 The Problem We are on Sitecore 10.1 update 2. We had a business requirement to allow HTML tags in single-line text fields so that page headings and subheadings can have superscripts etc. in them. We understand that for security reasons, Sitecore encodes all the HTML tags entered into the fields. This needed us to make sure to add logics in our backend to ensure that the HTML tags gets decoded so that they can be rendered at the front end. So far so good and everything went as planned. After the customization, we were able to see the HTML tags added to single-line text fields getting rendered properly at front-end.  Then where is the problem? We did a few more edits on the page and observed that HTML tags added to Single-Line text fields earlier got stripped off during subsequent edits and page saves. Here is a video of the issue -  The Research This issue was also reproducible on sandbox instances. This proved that it was not due to any of the customizations done in our ...

The Problem This issue can happen to developers who are trying to install the Sitecore 10 instance. Developers may start getting following error -   "Failed to start service Sitecore XConnect Search Indexer"  When developers will check in xConnect event log, they will observe that the exception is about a missing required. Below are entries in the log file for the same (XConnect.log file) -  2023-06-12 10:03:15.286 +05:30 [Error] Failed to start the indexer host System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Sitecore.Nexus.Licensing.LicenseException: Required license is missing: Sitecore.xDB.Base    at ‭‪‮‎‌‪‎‫‬‌‮​‍‪‎‬‎‏‌‫‭‮‮.(‬‮‍‎‍​‭‎‮‮‪‏‮‏‌‪‎‭‌‍‭‪‬‮ , String )    at Sitecore.XConnect.Configuration.Extensions.InitializeLicenseCheck(IServiceCollection collection, String licenseFileOrXml)    at Sitecore.XConnect.Configuration.Extensions.UseX...

Pretty much all the Sitecore development is happening in Agile. Hence, code is released more frequently to live servers than it used to be in waterfall models. This also means there is a need of testing after each release. A regression in QA environment and a smoke test in STAGE environment is required to ensure that the development done in sprint does not break any thing else. This is the job of QA team. Why are we talking about it here? If your team is testing Sitecore functionalities manually, then it is wise to automate at least some of your test cases. Testing some basic Sitecore functionalities like login, publishing etc. manually is something QA team can easily do but when one needs to automate it, QA developers needs to have some knowledge of Sitecore also and vice-versa.  Hence, here is a simple blog on guiding how to develop some basic automated test cases in Sitecore. Lets get started.. In this blog, I am taking example of a basic scenario which includes testing that you...

Hello friends! In this blog I am going to talk about fundamentals of Azure Functions.  Azure Functions is a server less solution that allows you to write less code, maintain less infrastructure, and save on costs. Instead of worrying about deploying and maintaining servers, the cloud infrastructure provides all the up-to-date resources needed to keep your applications running. Hence, main advantages of Azure Functions are -  serverless programming highly scalable low cost Azure Functions can be look on as Events + Code which means all we have to do is to write code and then tell Azure what trigger will run the code. A trigger can be a scheduler, a message in MessageQueue, a new item in blob storage, a http request etc. So how do we run code in Azure - Azure VM install whatever u want web servers, windows services etc IaaS complete control of the serverless choose your operating system You are responsible patching and maintaining scaling ...

 We are on Sitecore 10.1.2 and we use Sitecore Publishing Service module. We often encounter random unresponsiveness of Publishing Service where content authors report that they tried publish an item or a site but the publishing dialog seemed unresponsive and errored out as in snapshot below after few seconds - When we looked at the publishing service logs, we could see that it disposed off all the connections but did not attempt at recreating them. An application pool recycle solves the problem but the catch is this blocks the content authors from publishing their changes until a developer gets to recycle the application pool for the publishing service. We had an option of scheduled application pool recycle for the Publishing service but our application is used 24x7 across the globe by content authors for editing their content. So there were chances that application pool recycle may kill any publishing jobs and then create further problems. As an attempt to solve this problem, we ...