Ghanendra's Tips

This blog introduces you to concept of updating rendering and rendering parameters using Sitecore PowerShell Extension. If you are maintaining a web application based on Sitecore with loads of content items, you may be familiar with content cleanup or update requests that comes from business. This is where Sitecore PowerShell Extension comes very handy and saves our life. A little background .. We were using Media Framework based connector for Brightcove videos integration in Sitecore 8.2 website. When we upgraded to Sitecore 10.1, connector for Brightcove videos integration was also migrated from Media Framework to Data Exchange Framework. So far so good. But we realized that Media Framework based integration involved storing some video and video player related data in rendering parameters as in snapshot below -  We did not see these rendering parameters getting used anymore in Data Exchange Framework based integration. Hence, it was decided to remove these rendering parameters from r

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 (CI/

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 solution. We r

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.UseXConnectServiceInitializationConfigurati