THINK SITECORE WITH VAISHNAVI

  In this part, I will cover the implementation with the code.               As mentioned in the previous blog, We have to make changes to   Sitecore.XA.Feature.LayoutServices.Integration   to achieve it. Step 1: Create a new class file for patching with the name   BasicLayoutTransformer.cs Step 2: Copy the existing code from   Sitecore.XA.Feature.LayoutServices.Integration.Transformations.BasicLayoutTransformer Step 3: Modify the   BasicLayoutTransformer   class with the changes we need as per the requirement. Override the TransformElement method with the below code. Step 4: Add a config file that modifies the < transformer   type = " Sitecore.XA.Feature.LayoutServices.Integration.Transformations.BasicLayoutTransformer, Sitecore.XA.Feature.LayoutServices.Integration "   resolve = " true "  /> node with our newly created class and Namespace . ...

Sitecore SXA helps us to develop a site as fast as we can using the OOTB Component and it enables you to model your data in JSON. If you want to build a mobile app and feed it with SXA content, you can edit the JSON content on the page and have output content in JSON instead of HTML. I have faced a scenario that I wanted to blog about it. Existing: By default, SXA gives JSON responses for all the Pages on the site when we add  &sc_device=JSON  to the URL.  Problem: The JSON responses had default parameters like name, path, contents. But we had a requirement where I must return Grid setting, Styles and Variant configured in the Presentation Details. Existing JSON Output: Solution: We have to make changes to Sitecore.XA.Feature.LayoutServices.Integration to achieve it. Step 1: Create a new class file for patching with the name BasicLayoutTransformer.cs Step 2: Copy the existing code from Sitecore.XA.Feature.LayoutServices.Integration.Transformat...

Sitecore determines the default URL for an item based on its path, for instance the default URL for /sitecore/content/home/career/path/jobs is [sitename] /career/path/jobs . In some cases, it is useful to have shorter URLs that map to longer paths, for instance,[sitename]/jobs may be preferable as alternate URLs through a feature known as Aliases . To create an alias i n the Content Editor:  1. Go to Content Editor, click on the Page,  On the  Presentation   tab, in the   URL   group, click   Aliases . 2.  In the  Aliases  dialog box, in the  Name  field, enter the alias name. 3.  Click  Add. 4. W hen you have finished defining the aliases you want, click  OK . To create an alias i n the Experience Editor:  1. Click on the Page, Goto to Experience Editor ,  On the  Presentation   tab, in the   URL   group, click   Aliases . 2.  In the  Aliases  dialog box, in the...

We always have to worry about downtime or slowness in the website when the index is triggered. Our website search might stop or a few functionalities will be missing. You can set up Solr to rebuild an index in a separate core so that the rebuilding does not affect the search index that is currently used. Once the index’s rebuilding and optimization are completed, Sitecore switches the two cores to get the expected output. The SwitchOnRebuildSolrSearchIndex class inherits from the SolrSearchIndex class and adds the capability of maintaining two cores for a particular index. Sitecore switches the primary and secondary cores by sending a  SWAP  request to Solr. Please follow the below steps: Let’s have “sitecore_web_index” as the Primary core . Copy the “sitecore_web_index” in C:\solrx\server\cores_data and create a Secondary core named “sitecore_web_index_rebuild”. Similarly copy the “sitecore_web_index” folder in C:\solrx\server\solr and create another fol...