A key component of digital experience management is effective information retrieval. A simplified approach is required for websites, applications, and platforms containing a lot of material so that consumers can easily get the data they require. This need is met by Sitecore, a well-known name in the field of digital experience platforms (DXPs), which provides powerful and comprehensive search functionality. We will travel into the realm of Sitecore Search in this article, learning about its capabilities, architecture , and the enormous value it offers both developers and end users. Introduction to Sitecore Search A headless content discovery platform powered by AI , Sitecore Search enables you to build predictive and custom search experiences across various content sources. To extract and ...
Get link
Facebook
X
Pinterest
Email
Other Apps
Sitecore Error Troubleshooting: Sitecore 9.1 Current Content Database returns Master Database in Content Delivery Web Site
Get link
Facebook
X
Pinterest
Email
Other Apps
Sitecore Error Troubleshooting: Sitecore 9.1 Current Content Database returns Master Database in Content Delivery Web Site
Error Details: I was debugging the code base after sending the request from publishing website in Sitecore 9.1 and Sitecore.Context.Database was returning Master Database instead of Web database.
To troubleshoot the issue “Sitecore.Context.Database was returning Master Database”, I checked the Site definition configuration file to verify that site pointing to Master Database or Web Database and found that configuration was showing Sitecore website pointing to Web database”.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To troubleshoot more to identify the root cause of issue, I checked the configuration of Sitecore 9.1 website using the http://<host name>/sitecore/admin/showconfig.aspx:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In the above configuration file, I found that Site B pointing to Master Database with the help of role based configuration patch file:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was containing the Unicorn Source Folder related configuration details including the role base patch file for Standalone mode (a single Sitecore instance performing all server roles or local development environment) where database pointing to Master database.
Due to this rule-based configuration setting, Sitecore website Current Context was pointing to the Master Database instead of Web database. After removing this rule based configuration, Sitecore website current context start pointing to Web database when request coming from the published website.
This rule based configuration coming up with Habitat demo solution for Habitat Website and needs to be deployed on Development machine only and do not need to be pushed to the higher environments.
This article will provide the details about Sitecore GraphQL queries usage and how it will be useful in creating Sitecore projects especially Sitecore JSS projects. The topics covered under this Sitecore GraphQL article are: • Overview of Sitecore GraphQL (GQL) • Setup GraphQL (GQL) in Sitecore • Usage of Sitecore GraphQL (GQL) in Sitecore JSS • GraphQL (GQL) Queries Usage o Get an item by path and show field id and name o Return the name and value from all fields o Get the values of Treelist or Multilist field type o Get the template field details with values of current item o Get the field values using Aliases o Return a specific field with Alias ...
The Headless development in Sitecore is powered by a layer of services, API endpoints, and rendering SDKs: Services and API endpoints Sitecore Headless Services Sitecore Experience Edge for XM Rendering SDKs Sitecore ASP.NET Rendering SDK Sitecore JavaScript Rendering SDKs (JSS) In this article, we will explore about Sitecore scalable API layer called Sitecore Experience Edge which provides you a Sitecore-hosted GraphQL (GQL) API. With these Edge GraphQL (GQL) endpoint you can build your solution in any language and pull the required content with the help of GraphQL (GQL) . The major GraphQL APIs of Sitecore Experience Edge are: Preview API Delivery API You can check more details about these APIs at Type of Sitecore Experience Edge API . GraphQL is a query language for these APIs t...
Leading digital experience platform Sitecore offers strong capabilities for developing reliable websites and applications. The headless CMS and Jamstack architecture trends have been very popular in recent years. Sitecore provides Headless SXA (Sitecore Experience Accelerator) as a solution to decouple the front-end presentation layer from the content management capabilities since it recognizes the value of headless capabilities. In this article, we will guide you through the process of configuring a Sitecore Next.js multisite app and integrating it with Headless SXA in a Sitecore container. This setup allows you to leverage the benefits of Next.js, a popular React framework for server-side rendering, and the flexibility of Headless SXA for managing and delivering content. Table of Contents Step 1: Set Up the Sitecore Container Step 2: Add support for Sitecore SXA in Sitecore Headless Container setup St...
Comments