New answers tagged

0

This was useful for me in customizing the response: https://jss.sitecore.com/docs/techniques/extending-layout-service/extending-layout-service-overview. But, be very careful with it. It may break other JSS functionality here if you change it too much, which it looks like you want to. Adding fields is alright but changing the item serialization may take you ...


0

This has been addressed in JSS 16+ where hasLayout computed field has been added to query content items with layout. You can use this query below to get this result. { search(fieldsEqual: [{name: "hasLayout", value: "True"}]) { results { items { id name } } } } If you're in JSS 15 below you need to ...


0

I don't know how Sitecore.IndexRenderedContent plugin is exactly working but it's definitely not aware of the SXA local data sources (and probably about page relative data sources too). Try to resolve them manually: if (YOUR_DATA_SOURCE.StartsWith(Sitecore.XA.Foundation.LocalDatasources.Constants.PageRelativePrefix, StringComparison....


0

SXA JSS sites should not be defined in the configuration files. Instead, they are configured using Sitecore items. Please refer to this article for more details on how to manage JSS apps with SXA. Don't use jss deploy config command on an SXA JSS website. If you use it to deploy config for the graphql endpoint. Ensure the site and apps node are commented. &...


3

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. ...


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" />...


0

I faced the same issue in the JSS angular application. Make sure the component definition matches in the manifest and deploy the files. Check the component definition manifest.addComponent({ name: '**Article**' JSS deploy files - use this command


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 ...


0

I noticed on your tag Next.JS I guess you want to use JSS with NextJS. I am pretty sure next.js will not be fully compatible with Sitecore 9.3. My recommendation is to upgrade your solution to 10.1. Sitecore support will not help you if some issues appear because you are using not recommended versions of a module.


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 ...


0

Check you rendering on work item and see check if you are using caching there, if you don't require caching you can remove from rendering level or Item level, one more thing you don't need to see IISRESET, you can also check by https://sitecoreinstance/admin/cache.aspx, and clear cache Also if you want to have cache and wants changes to reflect then put your ...


0

In this case, the issue turned out to be that the object I was passing to the placeholder was incorrect. Before <Placeholder name="jss-contact-form" rendering={props} /> After <Placeholder name="jss-forms" rendering={rendering} /> What was confusing was that when I passed {props} to rendering, there was a console log saying ...


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 ...


5

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 ...


Top 50 recent answers are included