New answers tagged

0

Mistery solved. Kinda. To make sitecore root relative URLs work I needed to change value of Virtual Folder field in Settings of my "New site" from default "/" to some "/whatever". 🤷‍♂️


1

I stumbled across this while looking for a solution to the same issue and thanks to Mark's info I was able to get rid of the log spam by simply wrapping the GetMediaUrl in an extension method in which i'm foribly appending something that will be hashed with the media protection logic (so there will always be a hash value appended for places that I need it). ...


0

We solved the problem. As expected, it's a jQuery conflict. Here're the steps for to solve the conflict. We mapped the jQuery used by "Sitecore Forms" into a specific version. For this we created the file jquery.noconflict.js which contains only this single line of code. $jq213 = jQuery.noConflict(); We placed the file source to the 2nd position, ...


0

I fixed it with this: @Html.Sitecore().Field(PracticeAreas.Products.ProductImage, Sitecore.Context.Item)


1

I have answered the question you linked with some steps to troubleshoot this - but I will also answer here with an additional finding due to this question regarding SXA specifically. I found an issue where forms embedded in overlays in SXA (versions 1.9 and 9.3) will have this issue due to this bug in the component-overlay.js of the components theme which ...


0

Lol, I have the same problem yesterday and fixed it. Decompile the "RenderVariantField" pipeline in "Sitecore.XA.Foundation.RenderingVariants.Pipelines.RenderVariantField", patch the config that the pipeline points to your implementation ("patch:instead"). There are two problems: First Problem: Your Link field, like the default in the Link-Component, is ...


1

I don't think this can work out of the box. The search results component reacts on a signature. In order to match the results with the search box those signatures need to be empty or the same. The requests to the search API will work fine. But when the javascript gets the returned data, it will try to find the results component with your signature and it ...


0

The reason is that this part was move out from SXA configs settings <events> <event name="item:added"> <handler patch:after="*[@type='Sitecore.Data.Fields.ItemEventHandler, Sitecore.Kernel']" type="Sitecore.XA.Foundation.ContentValidation.EventHandlers.SeoUrlHelper, Sitecore.XA.Foundation.ContentValidation" method="...


1

There are two ways to accomplish this, use custom Scriban extension, see the following code sample: public class GetLinkUrl : IGenerateScribanContextProcessor { private readonly IContext context; private delegate string LinkUrlDelegate(Item item, string linkFieldName); public GetLinkUrl(IContext context) { this.context = context; ...


2

I think that this is a bug in Sitecore. Here's whats happening When you enable the CDN config, it sets Media.AlwaysAppendRevision to true This appends rev=xxx to all media urls The media request protection protectedMediaQueryParameters config has <parameter name="rev" description="media revision"/>. The media request protection code in Sitecore....


0

I had raised a Sitecore support ticket for this same issue and below is the response that I got. Please find below the documentation of how to include credentials on cross-origin requests for an SXA site: https://doc.sitecore.com/developers/sxa/19/sitecore-experience-accelerator/en/include-credentials-on-cross-origin-requests.html CORS functionality in ...


2

First of all, you don't need to have a delegate there. It is useful when your function can accept optional parameters. You won't do it in Func and that is why we are using delegate. Otherwise, you can do something like that and skip delegate: args.GlobalScriptObject.Import("sc_link", new Func<Item, string>((item) => { // something return ...


2

For me Sitecore.Sites.SiteContextFactory.Sites worked to get all sites. If you need to know whether it is an SXA site or not, you can check for the property IsSxaSite (something like x => !string.IsNullOrEmpty(x.Properties.Get("IsSxaSite"))


0

I believe only text field are supported, you will have to extend to support link/image fields: Have a look at following article: https://ggullentops.blogspot.com/2018/10/using-tokens-in-sitecore-sxa-variant.html?m=1 Regards Bryan


Top 50 recent answers are included