Ilma's Sitecore Blog

Checkout my Step by step guide to Establish Headless SXA Tenant, Site and Next.js app with Sitecore XP 10.3  Encountering this error in Sitecore indicates that we haven't configured our domain in IIS with the necessary HTTP or HTTPS settings. To resolve this issue, follow these steps: 1. Open IIS Manager. 2. Locate your site's domain. 3. Click on "Bindings." 4. Click on Add 5.Add a new binding with type HTTP and the hostname of your site. 6. Press the Windows key + R , type in " iisreset ," and then click OK. 7. Open a PowerShell script, navigate to the project directory, and execute " jss start:connected " 8. Now, open your web browser and visit http://localhost:3000; your site should be operational. Thanks for Reading!!

  Step 1: Prerequisites Installed Sitecore version 10.3  Check out Sitecore XP 10.3 Installation guide Configured an HTTP binding in IIS for your site (e.g., http://demo.dev.local - Next.js requires specific setup to connect to an HTTPS server) Installed Sitecore Powershell Installed Sitecore Headless Services  Checkout Headless Services Installation guide Installed SXA 10.3 Successfully populated Solr schema and built necessary indexes Ensured that you are running the latest version of Node Step 2: Create a Headless Tenant Go to the Sitecore Launchpad and click on ' Content Editor' button. To create a Headless Tenant, right-click on the ' sitecore\content ' and then choose ' Insert ' > ' Headless Tenant '. Input the Tenant Name (for eg, 'HeadlessSXATenant'), choose all modules , and then click ' OK '. To create a Headless Site, right-click on ' sitecore\content\HeadlessSXATenant ' and then select ' Insert' > '

  Introduction : Sitecore JavaScript Services is a toolkit for JavaScript developers allowing to build full-fledged customer solutions (SPAs, web apps, websites) using modern JS libraries and frameworks (React.is, Angular) by being completely unplugged from Sitecore. Install Sitecore JSS Service: Installation of Sitecore JSS Service is a breeze, especially if you've had experience installing packages in Sitecore before. Prerequisites: Valid Sitecore JSS License: To confirm if you possess a valid license, you can check your license.xml file for the presence of ' Sitecore.JSS .' Sitecore Version: For certain features like the JavaScript Rendering SDKs, such as Next.js, you'll require Sitecore 9.0 Update-1 or a later version. If you intend to leverage these features, it's recommended to have Sitecore newer version installed. In this blog post I am using Sitecore 10.3 Update-1. To install the JSS, make sure to follow the steps outlined below: Step 1:  Navigate to  Si

Prerequisite Installation Error During On-Premises Server Setup While setting up a on-premises server for Sitecore 9.2 Habitat project, I encountered the following error during the installation of the Sitecore prerequisites. It appears that Microsoft has relocated the download location for Web Platform Installer v5 . For our on-premises installation, Sitecore furnishes us with SIF scripts to automate the installation of prerequisites, sparing us the manual download and installation of all the required software on a new server. However, this time, Microsoft has changed the location and also renamed the .msi file, causing some complications. In the previous configuration found in Prerequisites.json for Sitecore 9.2, the following parameters were defined: Which should be updated to:  https://download.microsoft.com/download/8/4/9/849DBCF2-DFD9-49F5-9A19-9AEE5B29341A/WebPlatformInstaller_x64_en-US.msi After making these updates, the prerequisites will be successfully installed. Thanks for

In my previous blog, I shared a comprehensive, step-by-step guide on installing Habitat. During my installation process, I encountered an Error Code 1 while installing npm for Habitat as you can see in above image. In this new blog post, I'll delve into the root cause of this issue and detail the steps I took to successfully resolve it. Cause :  The culprit behind Error Code 1 was the version of gulp-sass specified in the package.json file. Solution : To tackle this issue, I first visited https://www.npmjs.com/package/gulp-sass to confirm the latest available version.  Afterward, I updated the gulp-sass value in the package.json file with this new version.  Then, I opened Windows PowerShell as an administrator and re-executed the " npm install " command. The " node_modules " folder was successfully added to the directory. Thanks for Reading !!