ClientLibs loaded twice on the Page | Community
Skip to main content
Level 4
Sep 13, 2019 8:06 AM UTC

ClientLibs loaded twice on the Page

Hi Team,

I have scenario for  clientlibs  loaded twice on the page

On Template Level :

Example :

categories = [Category1]

dependencies = [category2,category3]

On Component :

categories = [Category4]

dependencies = [category2]

While on page load, I see dependencies are loaded twice using domain abc.com but loaded only once on author and publisher instance which is really strange.

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

8 replies

ArpitVarshney
New Participant
Sep 18, 2019 8:31 AM UTC

Hi Sumit,

Yes,Ideally it should be loaded once on dispatcher as well.

There is some issue at the dispatcher only.Could you just clear the dispatcher cache of that page and give it another try?

Regards,

Arpit Varshney

Translate
Level 4
Sep 30, 2019 7:30 AM UTC

Hi,

Its not the dispatcher which is caching, I have clear the cache and still its not working.

Do you know think ,if any xyz component on parsys contains clientlibs and same clientlibs present at the template also can make the issue.?

Translate
PriyankaBiswal
Level 2
Sep 18, 2019 7:23 AM UTC

Hello,

As category 2 is already  loaded in the page, can you not remove the dependancy of category 2 from component's clientlib and see how it goes.

Translate
Level 4
Sep 30, 2019 7:26 AM UTC

Hey,

I already tried , but the issue is the variables which are used getting undefined error in the JS. As the JS loaded at the bottom of the page and the dependency is not able to find the variable above.

Thanks

Translate
Employee
Sep 13, 2019 3:10 PM UTC

Can you clarify when this happens ? When opening the page ?

Translate
Level 4
Sep 14, 2019 4:07 AM UTC

Yes on page opening .

When I checked view page source the clientlibs are loaded twice on the page .

Translate
Employee
Sep 14, 2019 3:32 PM UTC

Looks like something at dispatcher level might be causing the issue. Can you change the dispatcher log level to DEBUG and try to load the page?

It should show you all the requests and what might be causing the extra request.

Translate