Skip to content
Home » Resources Enhanced by Sitecore SXA with a Void Timestamp

Resources Enhanced by Sitecore SXA with a Void Timestamp

  • by
Resources Enhanced by Sitecore SXA with a Void Timestamp

Assets Optimized by Sitecore SXA, This article is committed to Sitecore SXA Resource Streamlining agent. 온라인카지노

Definitively, I need to impart to you how to determine the issue with a void timestamp boundary, which is liable for resources forming.


The Sitecore Experience Gas pedal has an underlying Resource Enhancer module that is utilized for upgrading CSS styles and JS scripts.

If you have any desire to further develop your site execution, you ought to empower this module in your creation climate

And it will chop down the volume of information that should be sent.

As a Sitecore chairman, you have two choices of empowering Resource Enhancer:
  • Worldwide enablement for the whole Sitecore example
  • Nearby enablement for chose locales

As indicated by the best practice, both CSS styles and JS scripts are stacked on the client side

With a rendition prefix to keep away from a reserve issue when another conveyance happens.

Furthermore, SXA isn’t an exemption:

It applies a timestamp for the upgraded resources, as displayed beneath:


In one venture I was associated with, we noticed the accompanying issue — the timestamp was not produced for limited destinations.

All enhanced resources contained the void timestamp boundary, as displayed beneath:

This outcomes in the circumstance when the client program doesn’t refresh the stored rendition of CSS styles and JS scripts. 카지노사이트

After another sending, since the t boundary is a forming component.

Thus, we should examine this case.


The primary thing we really want to do is to sort out how and where the timestamp is created.

A good thought is to begin from the default SXA design razor page. It’s called SxaLayout.cshtml.

As may be obvious, to get a resource interface, it executes the static GenerateLinks strategy for the AssetLinksGenerator type

(complete name: Sitecore.XA.Foundation.Theming.Bundler.AssetLinksGenerator)


Going further, we can find the GetOptimizedItemLink technique

Which is answerable for the resource connect age. It looks as displayed underneath:


In the return articulation, on the off chance that an enhanced content thing is both not invalid and unfilled

The BuildAssetPath() expansion technique is executed.

OK, we’ve found where the timestamp is added. Fascinating, it goes from the framework’s Updated format field.

Hm, what could be the issue with that? How about we really take a look at this field.

Alright, the Updated field has a place with the Insights format that is a piece of the Standard Sitecore layout.

The critical thing here is that this field isn’t shared. It truly intends that in the event that we have a site with no default limitation

Streamlined resources likewise ought to have this language form that is a piece bizarre — do we truly have to have restricted resources (CSS and JS)?

I don’t know. Thus, we want to apply a fix to determine this issue for limited destinations.

In the first place, we really want to make our own BuildAssetPath augmentation technique (a similar code as above)

  • With one extra line of code inside the if explanation:
  • Thing item1 = item.EnsureFallbackVersionIfExist();

This expansion technique (get together Sitecore.XA.Foundation.SitecoreExtensions.dll, ItemExtensions.cs)

Returns a thing for a default language (generally English) in the event that there are no language variants.

That is the thing we want for enhanced scripts.

Second, we want to make another sort (acquired from AssetLinksGenerator.cs) with the superseded GetOptimizedItemLink technique

And another static GenerateLinks strategy to conceal the base one. 카지노 블로그

Leave a Reply