Hot answers tagged

10

If you want the exact same component - that is not possible. That is probably referring to partial designs - which offer that functionality but those include the full component with its datasource. If you want to reuse components (or sets of components) and still be able to change the datasource, snippets might be a solution. They can be easily created (...


9

From numerous experiments, I have put together the following tips and tricks. Note that a good score under the desktop tab is considerably easier to achieve, the mobile score in our responsive sites is the real score we should benchmark against. Backend Vs Front End Page speed can be divided into two distinct parts. Backend server response and front ...


7

You need to create your custom rule for this. Create a class which inherits StringOperatorCondition: using Sitecore; using Sitecore.Rules; using Sitecore.Rules.Conditions; namespace ClientName.Foundation.SitecoreExtensions.Rules { public class IsExperienceEditorMode<T> : StringOperatorCondition<T> where T : RuleContext { ...


6

Yes! SXA 1.9 has a new feature called Design rules. You will find a new field on the Page Designs item: where you can design a rule which will pick up Page Design for you thanks to new "select specified page design" action. Here is an example rule: So right now we have two fields where you can select Page Design and the priority is a fallow: If Page ...


6

So after some back and forth with Sitecore Support, this is the conclusion and the solution. The fact that SXA ends up in the endless loop has been registered as a bug. Bug reference number #349107. The solution is this You need to add the site registration to SitecoreIdentity, making it a known entity for it to act on. We added the following configuration ...


6

SXA comes with a special package for the CD. If I recall correctly you simply unzip the package and dump out onto the server in the Sitecore web root. These instructions are documented in the installation guide. The master database is not used in the content delivery environment and often times that database is nowhere near it. Furthermore, Sitecore ...


6

You can answer this question on your own by using DotPeek. The GetSiteLevelCaching processor in GetRenderingCaching pipeline is responsible for processing those items. The code looks like this: public void Process(GetRenderingCachingArgs args) { ... var renderingId = args.Rendering.RenderingItem?.ID.ToString() ?? args.Rendering.RenderingItemPath; ...


6

Yep! You can do it by adding Rule item under your Sriban template item and using sc_evaluate function inside of the template. Example: I have a page which has two fields: Title Brand And I want to render Brand field only when it is Monday. In order to do that I'm using Page Content rendering (can be any other) with following rendering variant: And the ...


5

I had the same issue and was not able to resolve this with OOTB functionality. You could change the source field (query:$home) of the OOTB Search Box Template (/sitecore/templates/Feature/Experience Accelerator/Search/Rendering Parameters/Search Box/SearchCriteria/SearchResultPage) but this is not a recommended approach. Therefore, I created my own ...


5

You can add a new CSS class in the Rich Text Editor dropdown and apply it to the selected row table. There are two steps to add CSS class in RTE: Add element inWebsite\sitecore\shell\Controls\Rich Text Editor\ToolsFile.xml file. Now add the definition of that CSS class (eg. arrowlink) in Website\default.css file. You can see newly added arrowlink CSS ...


5

According to the documentation, https://doc.sitecore.com/developers/sxa/17/sitecore-experience-accelerator/en/trigger-creative-exchange-from-your-ci-server.html, as of SXA 1.7 there is support to import front end assets into Sitecore. First create a user with full admin access that is used to run SPE RestfulV2 services, then patch as follows <?xml ...


5

The redirect behavior in SXA only applies to sites managed by SXA. Consider the options typical of a non-SXA implementation but be aware of the risks and limitations of each. Examples Redirect in CDN/Proxy - difficult to apply for many 1-to-1. Cloudflare for example limits the number of available page rules. IIS Rewrite module - Low complexity for large ...


4

With Azure search - if you use contains then it does a partial word match as in "Samp" will boost "Sample Page 1". If you use "Sample" it is not a partial word so does not get boosted. To use the word matching in a phrase you need to use is equals to rule. I also discovered that the "is case-insensitively equal to", "is not case-insensitively equal to", ...


4

Instead of downloading Powershell Extensions 5.0 from Sitecore Marketplace, need to download the "Sitecore PowerShell Extension 5.0 for Sitecore 9.2" package from the same page where you got the SXA package. SXA 1.9 Download page Apparently the Powershell Extensions here are a different build than the one on Marketplace, and it resolves the error.


4

You should use the AnalyzingInfixLookupFactory , see below section. Please note the lookupImpl and dictionaryImpl fields. The AnalyzingInfixLookupFactory is currently supported by SOLR 7.5 - Context filtering lets you filter suggestions by a separate context field, such as category, department or any other token. The AnalyzingInfixLookupFactory and ...


4

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


4

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

You need to place the content inside the overlay placeholder instead of the main placeholder.


3

Sitecore 9.2 requires Sitecore Experience Accelerator (SXA) 1.9, not 1.8. SXA 1.9 for Sitecore 9.2 requires either: The official Sitecore Powershell Extensions 5.1 version: https://github.com/SitecorePowerShell/Console/releases/tag/5.1 The SXA build of Sitecore Powershell Extensions 5.0 for Sitecore 9.2: https://dev.sitecore.net/Downloads/...


3

You have 2 main options: Use a placeholder In your razor view, just add a placeholder, then in the Experience Editor, your marketers/editors can add the Social Media Share module to that. Pros - its nice and easy, give flexibility too if you wanted to add anything else. Cons - the editors have to remember to add the component every time. Render the ...


3

I'm still new to using SXA so take my opinion with a grain of salt. I will provide some examples to explain my position. What I can say is that there are enough benefits to using SXA that I would recommend it but I can't say it's all green grass and rose petals. There's quite a learning curve as it relies a lot on SPE to create many things which aren't ...


3

When creating a new site within your tenant, you can (de)select the modules you wish to add to your site. These are the default modules available (SXA 1.9) when adding a new site: After your site was created you can always add modules which were not selected when the site was created. Add modules to tenants and sites using context menu script (Add ...


3

That is quite simple, you need to use PresentationContext service. Here is an example: ServiceLocator.ServiceProvider.GetService<IPresentationContext>().GetDesignItem(CONTEXT_ITEM); It will do all the work your you: check if there is design selected on your page check design rules and at the end check Template to Design Mapping field (if design won'...


3

Modification of results items before sending them to the front-end scripts might be hard in SXA 1.7. You would need to: override SearchController and modify GetResults() method - this method is building a query, getting items and preparing ResultsSet which later on is sent to the front-end replace controller in DI container It is possible but I do not ...


3

To fix this, Verify following are set up correctly Valid SXA licence is present Make sure the host name in /sitecore/content/Sitecore/Storefront/Settings/Site Grouping/Storefront is correctly configured to the web site you are browsing the sitecore in. Make sure the template of the home item is inheriting the home page configuration template.


3

Did you try populating Solr Managed Schema from Sitecore Control Panel? After creating a custom index in Solr and configuration file in Sitecore, this should be the next step. Once successfully populated, try rebuilding the index.


3

SetImageStyleParameters from Sitecore.XA.Foundation.SitecoreExtensions.Pipelines.RenderField is responsible for that. It is used to add HSpace and VSpace from image properties. I don't know which version of SXA are you using but in the newest version, it should not add any additional margin when both HSpace and VSpace are 0. If you don't need it, simply ...


3

There is no configuration to enable/disable asset optimization on a theme/file level. SXA Theming and the Asset Optimizer considers the files uploaded under Scripts and Styles for optimization and to load on the website. You need to upload your file outside this location and refer accordingly.


3

Apparently the SitePhysicalPath is transferred en used in all of Sitecore jsons, but not in the one from SXA. Quick fix: open SXA-XP0.json and find the Site.PhysicalPath variable (line 69). Adjust it to the path you installed the site, something like: "Site.PhysicalPath": "[joinpath(environment('SystemDrive'), '...', '...', 'wwwroot', parameter('SiteName')...


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.


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