New answers tagged

0

if you have a Custom layout (which probably you do), the easiest way is to add @ AssetLinks assetLinks = AssetLinksGenerator.GenerateLinks(new ThemesProvider()); if (Sitecore.Context.PageMode.IsExperienceEditor) { foreach (string style in assetLinks.Styles) { @Html.Raw(style) } foreach (string script in assetLinks.Scripts) { @...


1

It is working fine on the latest version. Both Search Results and JSON Results are using custom index (both of them are using IndexResolver to get proper index). If this doesn't work on an older version you will need to request a hotfix. Please contact Sitecore support.


1

Got the fix for my issue. Basically in original js for tabs line number 247 was causing the auto scroll. So added an unique class ('dummy-focus' here) in the top container of page and added the script const element = document.getElementsByClassName('dummy-focus')[0]; element.scrollIntoView(); after $tabNav.first("li").focus(); (line 247)


0

Your errors occurs when fetching the rendering parameters of the LanguageSelector component. The "Item with the same key" refers to the fact that the a duplicate key is found when the code tries to read the parameters and place them in a Dictionary object. As I never believe and "suddenly" and "supposedly" (editors never made a ...


0

No, that is not possible. The whole logic (scopes, boosting, ...) can be used only by SXA search renderings at the moment.


3

I'm glad you asked! Turns out that there is very interesting explanation for this. When using the Caching.CacheKeyIndexingEnabled.ItemCache setting a call to retrieve all the sites is performed. This is needed to clear the filter cache for each site. As you can see below, there is some validation on the database configured in the site definition. Sitecore ...


0

The AND or OR operators in between the parts of your query are placed based on the Operation as set in the SearchStringModel. In your case, the Operation is set to "must" - which is an AND. If you want an OR, you can use "should" here: protected virtual SearchStringModel BuildModel(string fieldName, string value) { var name = fieldName; ...


0

I found that by adding the template to the experienceAccelerator/getVariants/allowedTemplates in a configuration file seemed to make this work.


2

As you mention 9.2 we can assume this is a NVelocity template. As Vlad mentioned, you can use a foreach loop there as shown here: http://people.apache.org/~henning/velocity/html/ch05s04.html <ul> #foreach( $product in $allProducts ) <li>$product</li> #end </ul> Note however that 9.2 is the last version that support NVelocity ...


0

I solved this problem by extending a link tool we built (initially for NVelocity) for Scriban. A member of the community shows how to do the migration here. Here you can see several methods exposed to help build the various parts of the link. <div class="field-link"> {{ $linkUrl = sc_linkTool.get_field_link_url i_item "Link" }} ...


0

If you want to limit the results of your search, you need to use the scope and not the boost as that will not limit (just boost). So you need to add the tag requirement to the scope where you now only have the template. You might be able to use the out-of-the-box SXA tokens in the search scope to match your needs. Check out the documentation here: https://...


0

For this issue, I connected with Sitecore Support, and they have admitted it as a bug. Please see below their response. Thank you for contacting Sitecore Support! During the investigation, I was able to reproduce the issue in my local environment. The behavior you reported was registered as a bug in our bug tracking system. Thank you for reporting the ...


1

I'm not sure if I exactly known what you are trying to achieve but here are some details which might be helpful. The BoostingService has two important methods: IQueryable<ContentPage> BoostQuery(IList<Item> boostingItems, string searchQuery, Item contextItem, IQueryable<ContentPage> queryable) IQueryable<ContentPage> BoostQuery(Field ...


0

So far I have managed to pinpoint what is causing the issue on not returning search result when a facet value includes "/" and "&" characters. Decompiling Sitecore.XA.Foundation.Search.dll helped me to see the pipelines used in search and facet filtering. The culprit was Sitecore.XA.Foundation.Search.Pipelines.EncodeFacetValue....


0

This happens when you have a rendering in the placeholder in a partial. So if your partial has a component in the main placeholder, the user will be unable to add that component to the placeholder in the content pages.


Top 50 recent answers are included