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 (...
You need to create your custom rule for this.
Create a class which inherits StringOperatorCondition:
public class IsExperienceEditorMode<T> : StringOperatorCondition<T>
where T : RuleContext
Yep! You can do it by adding Rule item under your Sriban template item and using sc_evaluate function inside of the template.
I have a page which has two fields:
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 ...
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')...
There is no ootb exact check for page mode - you could write it yourself if you want. Or you could try to work with the querystring parameters. Not sure if that is always correct, but a quick test seemed to work with a rule like this:
where the sc_mode request parameter is case-insensitively equal to edit
The sc_mode parameter normally has the page mode - ...
Make sure you have the below configurations in place:
A page design created for the page and your custom theme is assigned to it.
Page design assigned to the page item.
Make sure your site's compatible themes settings are proper under the settings item.
Make sure your custom CSS file is under the Styles folder of the Theme. SXA loads the CSS files uploaded ...
Facet filters are using values for the index. If inside of the index, the _language field has language codes :
then you will see language codes in the dropdown. What can be done here:
use custom field with language
try to find an existing field which has full language name instead of code. I noticed that there is a field called paresedlanguage. I have no ...
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.
I don't think you can do this ootb... unless you are on 9.3 and are able to use Scriban.
There is a workaround though - but it's a dirty hack and maybe not upgrade-proof. I used to have an issue where I had to use a data attribute in a section to get a value from a referenced item - which also didn't work as those attributes work on text fields only.
I had this bug in SXA 1.7.1. The issue was that deleted items did not get removed from the index (apparently the SXA implemention was missing a null check).
The result of the bug is indeed that items do not get removed from the index, unless you do a rebuild of the sxa index. This makes the count wrong (as that goes by the index) but not the results as SXA ...
Which version of SXA are you using?
Based on what I have come across, _HasValidUrlName is used in Sitecore.XA.Foundation.ContentValidation to check if the item being created is inherited from _HasValidUrlName template but it doesn't check for what you are looking for atleast in Sitecore SXA 1.8
public struct _SeoUrlValid
public static ID ID = ID.Parse(...
I had exactly the same issue and 'fixed' it by creating an extension method that creates a new LinqToCloudIndex<TItem>. I say 'fixed' because I was not able to identify the exact cause of the problem. But by recreating the LinqToCloudIndex I was able to overcome the error. The best solution would be a proper fix by Sitecore.
Here are the details of my ...
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 ...
A while after I originally asked the question the SXA Team added a boosting feature.
One consideration to make is that the boosting will change the sorting. If you are sorting based on Geo Location then you may see more relevant results higher in the list than those that are nearer to the search location. Using the boost would be ideal in a Site Search ...