New answers tagged

0

Out computes field sxacontent is defined as a textCollection because, in fact, it is an array of texts. This field is gathering content from the whole item and its fields. It is not only e.g.: content of a Title field but you will find much more texts from your item. If you want to change something, for example: implement your own tokenizer in Solr and ...


0

Rendering Variants are created under the path: /sitecore/content/[Your tenant]/[Your site]/Presentation/Rendering Variants/[Feature name]. As you are looking to modify/add rendering variants to Navigation component, the path should be /sitecore/content/[Your tenant]/[Your site]/Presentation/Rendering Variants/Navigation as shown below:


1

When you will create a new site, you will have all of the Rendering Variants defined under your Site, here: We have also a few "global" variants which are here: /sitecore/system/Settings/Foundation/Experience Accelerator/Rendering Variants/Rendering Variants but in general you should use your own one. So the one which will be auto-created in the site ...


0

A SXA rendering can return html or json, but to use the variants system your model needs to have the data so the variants can access that and turn the data into html. From a quick look at your code you need: make sure your custom properties on the model are filled on the right place (you are now doing this in the GetEvents which is not the right place - ...


0

The $xaRichTextProfile token is resolved in the Sitecore.XA.Foundation.Editing.Pipelines.ResolveTokens.ResolveEditingTokens processor. It basically gets the profile path form XA.Foundation.Editing.DefaultRichTextProfile setting. If that setting doesn't exist or will be empty it will fallback to /sitecore/system/Settings/Html Editor Profiles/Rich Text XA ...


0

Maybe I'm missing something but you can already create a local data source for Tabs. Just drop Tabs on the page and it will ask you were to create its data source: And it will create data source item here: If you would like to have local data source created automatically for your Tabs rendering you can also do it. Find the rendering item and add this ...


0

SitemapHandler which internally is using ISitemapGenerator is the entry point. It has a virtual GetSitemap method which is looking for an instance of ISitemapGenerator in the DI container. So it should pick up your implementation if you have correctly replaced an instance of ISitemapGenerator in the container. If the above config patch is not working for you ...


0

This was raised as a bug - Sitecore reference 362491. The workaround was to have rule based display of the variant fields:


1

This is a problem that falls on the unfortunate spot in between SXA, JSS, and Sitecore Services Client. I know it doesn't help you to know that these are somewhat separate development teams inside Sitecore, but I do believe that's where this falls. Using the new SXA/JSS features in 9.2 and above, we've also found that some Api calls and GraphQL calls fail ...


3

This can happen if you have made your SXA Tenant unpublishable. There seems to be some logic in some components that doesn't resolve the Context (master/web) correctly and needs to have the site published. Simply make your SXA Tenant publishable (remove publishing restrictions) and publish to resolve this issue.


0

You can accomplish this with a bit of a workaround. In order to do it you need to first understand how overlays work. Overlays first check if there's any item with the class overlay-source on the page if so the javascript creates an overlay wrapper. and then upon clicking of an item the overlay gets loaded into that overlay wrapper. In both the search ...


0

I guess, I got the root cause. I had site definition in config file. Sxa will look for site definition inside the setting item of site and sxa will get error if you have same site definition in config file. This should be log in the log file


0

Although rebasing seems to be a quite complex task, I selected the solution that merges 2 home nodes together. In my case I have the following website structure: My old home page is called home and the new one has name New Home. There are 3 main steps implemented in Sitecore Powershell: Create a copy of home and move its /Data/* children to the new copy ...


3

Ok, having spent some time trying to figure out how this whole thing works in Sitecore, I can now say, that SXA-JSS does not support integrated GQL. The problem lies in the sxa-jss configuration for the LayoutService, which is selected by default when you create a new SXA JSS site. The configuration above comes from this file: \App_Config\Modules\JSS SXA\...


Top 50 recent answers are included