Restrict loading of clientlibs-jquery

Avatar

Avatar
Validate 10
Level 2
v1101
Level 2

Likes

4 likes

Total Posts

150 posts

Correct reply

0 solutions
Top badges earned
Validate 10
Validate 1
Ignite 1
Give Back 5
Give Back 3
View profile

Avatar
Validate 10
Level 2
v1101
Level 2

Likes

4 likes

Total Posts

150 posts

Correct reply

0 solutions
Top badges earned
Validate 10
Validate 1
Ignite 1
Give Back 5
Give Back 3
View profile
v1101
Level 2

17-07-2020

Hello All - Following clientlibs are getting loaded in publish eventhough it is not added as part of our project specific clientlibs. Becasue of these clientlibs loading, it is causing issues with project specific clientlibs. is there a way to restrict these clientlibs in publish.

 

/etc.clientlibs/clientlibs/granite/jquery.min.js
/etc.clientlibs/clientlibs/granite/jquery/granite.min.js
/etc.clientlibs/foundation/clientlibs/jquery.min.js

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

646 likes

Total Posts

607 posts

Correct reply

239 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile

Avatar
Establish
MVP
BrianKasingli
MVP

Likes

646 likes

Total Posts

607 posts

Correct reply

239 solutions
Top badges earned
Establish
Ignite 1
Give Back 5
Give Back 3
Give Back 10
View profile
BrianKasingli
MVP

19-07-2020

@v1101, This looks like an unwanted client library of "cq.jquery" is being called within your page. 

How to solve: You need to look at your project files, structure basepage, components, and/or project client library configurations to find a reference of the "cq.jquery" name. If your codebase does not have such values in your project, then you should take a look at the resourceSuperType cq:component scripts and/or client libraries being referenced within the different resources within CRX/DE. Understand what, where, and who is actually including the "cq.jquery" client library would be the first step of removing this unwanted set of libraries.

Once you have found the underlying cause, your next step is to overwrite the resource's script file that includes "cq.jquery", by overlaying (if it is a script file) or to simply edit the client library that is referencing the "cq.jquery" client library name.

I hope this helps.

 

 

Answers (2)

Answers (2)

Avatar

Avatar
Establish
MVP
Ravi_Pampana
MVP

Likes

197 likes

Total Posts

243 posts

Correct reply

75 solutions
Top badges earned
Establish
Contributor
Shape 1
Ignite 5
Ignite 3
View profile

Avatar
Establish
MVP
Ravi_Pampana
MVP

Likes

197 likes

Total Posts

243 posts

Correct reply

75 solutions
Top badges earned
Establish
Contributor
Shape 1
Ignite 5
Ignite 3
View profile
Ravi_Pampana
MVP

18-07-2020

Hi,

 

Just to add to the above answer check whether you have included 

 

<cq:includeClientLib js="cq.jquery"/> in your project jsp or added cq.jquery category as embed or dependency to any of your project clientlibs

Avatar

Avatar
Validate 1
MVP
ArpitVarshney
MVP

Likes

136 likes

Total Posts

185 posts

Correct reply

36 solutions
Top badges earned
Validate 1
Establish
Give Back 5
Give Back 3
Give Back 25
View profile

Avatar
Validate 1
MVP
ArpitVarshney
MVP

Likes

136 likes

Total Posts

185 posts

Correct reply

36 solutions
Top badges earned
Validate 1
Establish
Give Back 5
Give Back 3
Give Back 25
View profile
ArpitVarshney
MVP

18-07-2020

Hi @v1101 

 

Could you please validate if any of your project client-lib has dependency property pointing to AEM jquery clientlibs like cq.jquery or cq.jquery.ui which might call these clientlibs in publish?

For debugging in LOCAL, You can just remove your project specific clientlib category from code and validate it if it is still appearing. If not appearing then probably your project specific clientlib is calling them in publish.

 

Regards,

Arpit Varshney