Sitecore Pantar

  The right to be informed – One Trust vs Sitecore •         Sitecore •         No Automatic scanning of cookies. They have to be manually identified and categorized or use some third-party tools. •         Cookie banner and setting etc have to be custom built using preferred technologies like Sitecore MVC , boot strap etc. •          Sitecore recommends capturing and storing your end customer’s affirmative action in the Sitecore Experience Database(xDB). This action can be stored as a facet on the end customer’s contact record in xDB. Once stored in xDB it is possible to display the contact’s information in the Sitecore Experience Profile •         One Trust •         Automatic Scanning of the website to identify and categorize the cookies used •         There are limitations for scanning pages that are behind Authentication •         Scripts are provided to integrate One Trust to Sitecore both for Test and Production environments •         Cookie banner , cookie settings a functions

  How to go to a Complete Sitecore Cloud Native from Sitecore XP. Introduction   In this blog, I’ll try to explain the need to consider going towards a Sitecore Cloud Native solution while upgrading your Sitecore solution to 10.x version & also a high-level road map to get there. Why Sitecore Cloud Native? ·        Tech landscape will be in line with industry trend Microservices-based, API-first, Cloud-native, and Headless (MACH) compliant ·        Sitecore CDP is better and more advanced integration and analytics (in line with current trend of “cookie less marketing”) ·        Sitecore Cloud Native solution is completely different from the way XP works. Here we can plug and play SaaS Components like Personalize, send etc as and when required. ·        Whereas Sitecore XP license brings in all the components as it is a monolithic architecture & in most cases the Out of the box features are never used or underutilized. ·        No more worries about platform upgr

    The Sitecore path analyzer was not showing up any data and the error logs show lots of errors.  For e.g.   [Path Analyzer] Error during aggregation.   Steps to resolve: Check the xdb.processing.tasks and xdb.processing.pools to  ConnectionStrings.config of CM Server. If it is not available, then configure them. Restart the app services On the reporting database run the query to delete the tree definitions using SQL Server Management Studio  Delete from TreeDefinitions Use the admin tool to Redeploy the Map definitions ( https://<sitecore-cm-url>/sitecore/admin/PathAnalyzer.aspx ) Use the admin tool to Historic map rebuild  ( https:// <sitecore-cm-url>/sitecore/admin/PathAnalyzer.aspx )  

    1.        Backup Size crossing the threshold a.        Problem The Microsoft threshold for backups is 10 GB. Sometimes there are situations encountered where the Web App size has crossed this limit and because of which the backups would fail. b.        Solution All files from /App_Data are either:   ·          Temporary files for caching purposes ·          Diagnostic data for debugging purposes They shouldn't affect any Sitecore functionalities if they are not restored from the backup files. But in case if there are any missing files from /App_Data in the future, some of them would automatically populate itself with data.   Create a Backup Filter 1)        Create a file named _backup.filter in D:\home\site\wwwroot through Kudu console ( https://<app-name>.scm.azurewebsites.net/DebugConsole) 2)       Add the following file paths in to the _backup.filter file   \site\wwwroot\App_Data\debug \site\wwwroot\App_Data\DeviceDetectio

  There was a vulnerability reported related to robots.txt during a pen test. In this case, it has been detected that information is being disclosed about the path of the sitemap.xml file which list all the endpoints of the application. In the same vein, sitemap.xml reveals information about the features of the application's private section.   To resolve the solution was to limit access to .xml files, which is suggested by Sitecore https://doc.sitecore.com/xp/en/developers/93/platform-administration-and-architecture/limit-access-to-xml,-xslt,-and-mrt-files.html But in spite of updating the web.config with the handlers mentioned below the Sitecore website was ignoring the handlers and still continuing to process the sitemap.xml like a normal request. <add path="*.xml" verb="*" type="System.Web.HttpForbiddenHandler" name="xml (integrated)" preCondition="integratedMode"/> <add path="*.xslt

Introduction Sitecore Assessment or Audit is a tedious exercise and here I’m trying to provide a high-level framework to carry out this activity. Of course, this would not be one size fit all kind of template, but it can certainly be used as guide or a template when conducting such audits. Bear in minds that such Quality assessment templates needs to be tailored to suit a particular project considering the environment, Technologies used, Sitecore version, Topology, System integrations and so on. When to do a Sitecore Assessment or Audit? ·          If the current partner did not deliver a quality implementation & if you are thinking of switching over to a new implementation partner, then it is certainly a good idea to conduct a Sitecore Audit to understand how bad or worse the situation is & also to decide on the next steps ·          As a pre cursor to any Sitecore upgrade activity or Cloud migration activity ·          As a regular hygiene, conduct an Sitecore Assessment or