Hot answers tagged

4

SIF Script is trying to access a site with http but you have only https in your bindings. In sitecore-xp0.json you have next definition: "UpdateSolrSchema": { "Description": "Update the solr schemas.", "Type": "SitecoreUrl", "Params": { "...


4

The Page Design that you're seeing isn't processed by the React application, it's just part of the default Item serialization. The power of SXA's Page + Partial Designs will translate into a list of placeholders, components, and nested placeholders in the JSON, no different than a non-SXA site. You need to start off with ensuring your JSS Layout definition ...


2

You can change this behavior by updating the "languageEmbedding" setting in the LinkManager configuration (asNeeded, always, never): <sitecore> <linkManager> <providers> <add name="sitecore"> <patch:attribute name="languageEmbedding" value="always" />...


1

I achieved this using wildcard-item in sitecore. I created like below, Below list of working urls. http://a-custom-route.com/articledetail/id1 http://a-custom-route.com/articledetail/id2 Note: Please handle your content retrieval logics as per id display in the URL(/articledetail/{id}). Handle this logic in a component and map with wild card item. ...


1

Welcome to Sitecore Stack Exchange. I wouldn't recommend trying to install unsupported JSS version, even if you succeed on making it work if you find any issues related to the module you won't be able to get official help for example from sitecore support. Depending on your current website installation (mostly if you need to migrate xDb data) I would rather ...


1

I have performed an investigation on how Sitecore adds the values to the route. As of now, I've found 2 ways of adding custom data to the route node: Extend the GetJsLayoutRenderer and override the RenderItem Change the serialization transformer. For your case, the quickest way is to use the second option. The first one will require more customization on ...


1

After analyzing the stack trace, I was able to isolate the culprit within the Sitecore.LayoutService.Analytics.config file. There is a processor named: Sitecore.LayoutService.Analytics.Pipelines.MvcRequestBegin.DetermineTrackerEnabled that is explicitly referencing the Tracker. Since I am using the XM topology, the Tracker dependency is not available and ...


1

Instead of targeting the _templatename field you should target the multi-valued _templates field which contains the inheritance tree for an item. Since this will get translated into a Solr query, despite the fact that we're using the "fieldsEqual" argument the field only needs to contain the value, which is perfect for our inheritance filtering use ...


Only top voted, non community-wiki answers of a minimum length are eligible