Skip to main content

Featured post

XM Cloud content sync from prod to uat or UAT to prod step by step

When working with Sitecore, it’s common to need content synchronization across environments. Today, I’ll walk you through the steps to sync content from Production to UAT/TEST and vice versa. Steps to Follow 1. Set Up Your Workspace Create a folder on your computer where you will manage the script files and exported data. Open the folder path in PowerShell to begin scripting. We need to run some scripts in PowerShell to update the folder with the basic requirements for syncing content. PS C:\Soft\ContentSync> dotnet new tool-manifest PS C:\Soft\ContentSync> dotnet nuget add source -n Sitecore https://nuget.sitecore.com/resources/v3/index.json PS C:\Soft\ContentSync> dotnet tool install Sitecore.CLI PS C:\Soft\ContentSync> dotnet sitecore cloud login If the above error occurs, you will need to run a different command to resolve the issue. PS C:\Soft\ContentSync> dotnet sitecore init now, Again run above command to open and authenticate with XM Cloud. It will be there a...
Post a Comment

how to fix Sitecore JSS Experience Editor Issue in branch template

 We can fix the branch template experience editor by using below config changes.

sitecorePath - change the branch template folder path

folder need to create by using template - 

/sitecore/templates/Foundation/JavaScript Services/App 

<app role:require="Standalone or ContentManagement" name="branchTemplateApp"

                     filesystemPath="/dist"

                     sitecorePath="/sitecore/templates/Branches/Newbranch"

                     useLanguageSpecificLayout="true"

                     graphQLEndpoint="/api/branchTemplateApp"

                     inherits="defaults" />


role:require="Standalone or ContentManagement": This attribute specifies the roles required to access the app. In this case, it indicates that users need to have either the "Standalone" or "ContentManagement" role to interact with the app.


name="branchTemplateApp": This attribute assigns a name to the app, which likely helps identify it within the Sitecore solution.


filesystemPath="/dist": Indicates the path in the filesystem where the app's files are located. In this case, it's pointing to the "/dist" directory.


sitecorePath="/sitecore/templates/Branches/Newbranch": Specifies the Sitecore path where the branch template is located. It's pointing to the specific location within the Sitecore content tree where the template "Newbranch" exists.


useLanguageSpecificLayout="true": When set to true, this attribute indicates that the app uses language-specific layouts. This can be essential for multilingual sites where different languages have their own layout definitions.


graphQLEndpoint="/api/branchTemplateApp": Defines the GraphQL endpoint used by the app. GraphQL is often utilized in Sitecore JSS for querying data. This endpoint seems specific to the "branchTemplateApp."


inherits="defaults": This might refer to inheriting default settings or configurations for this app from some predefined defaults.


This configuration appears to be defining an app within Sitecore JSS for handling branch templates ("Newbranch") within the Sitecore content tree. It's setting up access roles, filesystem paths, Sitecore paths, GraphQL endpoints, and other properties necessary for the app's proper functioning in the Experience Editor.


By ensuring that these attributes are correctly configured, it likely resolves issues related to the Experience Editor when working with branch templates in Sitecore JSS.

Labels:

Comments

Post a Comment

Popular posts from this blog

List of pipeline in Sitecore and it's example

 List of pipeline in Sitecore and it's example Sitecore uses a pipeline architecture to process requests and manage the flow of data within the system. Here is a list of some common pipelines in Sitecore, along with an example for each one: HttpRequestBegin: This pipeline processes the initial request made by a user to the Sitecore website and sets up the environment for processing the request. For example, it might determine the language for the request based on the user's browser settings or the URL . HttpRequestProcessed: This pipeline processes the request after it has been processed by Sitecore and is used to perform any post-processing operations, such as logging or error handling. For example, it might log the request information to a database for later analysis. RenderLayout: This pipeline processes the layout for a page and is responsible for rendering the components of the page, including the header, footer, and content areas. For example, it might retrieve the layout...
Post a Comment
Read more

Fileupload using AngularJS in asp.net c#

Fileupload using AngularJS in asp.net c# AngularJS built-in ng-model directive. I added an attribute called ng-files in to the file input element. Now, I need to  create a directive in the controller matching with the attribute  The attribute has a function named getTheFiles() with a parameter $files . I’ll initialize the parameter $files in my directive and later call the function getTheFiles() using the controller’s scope, along with $files parameter. <!DOCTYPE html> <html> <head>   <title>AngularJS File Upoad Example with $http and FormData</title>   <script src="http://ajax.googleapis.com/ajax/libs/angularjs/1.4.4/angular.min.js"></script> </head> <body ng-app="fupApp">     <div ng-controller="fupController">         <input type="file" id="file1" name="file" multiple        ...
Post a Comment
Read more

How Directives are compiled in angularjs?

AngularJS always operates on DOM node. We are not able to do any notice when HTML page loads. It parse automatically into DOM. Compilation of HTML happens in three steps which is pointed below. 1.    In angularjs $compile is use to traverse the DOM and looks for directive. It find each directive and add it into the list of directive. 2.    It is use to sort the list of directive by their priority when the entire DOM has been traversed. Each directive has own compilation function to be executed and each have chance to modify by itself. Each compile function return linking function and then it is use to composed into combined linking function and return it. 3.    $compile relations the template with the choice by calling the joint linking function from the earlier step. This in turn will request the connecting function of the separate directives, process listeners on the elements and set up $watch with the scope as each directive is organised to...
Post a Comment
Read more

XM Cloud content sync from prod to uat or UAT to prod step by step

When working with Sitecore, it’s common to need content synchronization across environments. Today, I’ll walk you through the steps to sync content from Production to UAT/TEST and vice versa. Steps to Follow 1. Set Up Your Workspace Create a folder on your computer where you will manage the script files and exported data. Open the folder path in PowerShell to begin scripting. We need to run some scripts in PowerShell to update the folder with the basic requirements for syncing content. PS C:\Soft\ContentSync> dotnet new tool-manifest PS C:\Soft\ContentSync> dotnet nuget add source -n Sitecore https://nuget.sitecore.com/resources/v3/index.json PS C:\Soft\ContentSync> dotnet tool install Sitecore.CLI PS C:\Soft\ContentSync> dotnet sitecore cloud login If the above error occurs, you will need to run a different command to resolve the issue. PS C:\Soft\ContentSync> dotnet sitecore init now, Again run above command to open and authenticate with XM Cloud. It will be there a...
Post a Comment
Read more