Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

Why is /foundation/jquery-ui.min.js loading on the Publish instance?

Avatar

Avatar
Boost 1
Level 1
oscarr38307878
Level 1

Like

1 like

Total Posts

13 posts

Correct Reply

1 solution
Top badges earned
Boost 1
Affirm 1
View profile

Avatar
Boost 1
Level 1
oscarr38307878
Level 1

Like

1 like

Total Posts

13 posts

Correct Reply

1 solution
Top badges earned
Boost 1
Affirm 1
View profile
oscarr38307878
Level 1

16-07-2020

We are trying to cleanup some of the unnecessary dependencies we inherited from legacy CQ5.6.1. We noticed there was a list of jquery-ui.min.js/css loading on the public pages. We understand all /libs, /foundation client libraries serve mostly authoring; therefore we want to start removing some of these from publish instance. Primarily the jquery-ui.

Can you help us understand how are we bringing this into the Publish instance?

We checked the following categories:

cq.jquery, jquery, granite.jquery, cq.foundation-main, cq.foundation, jquery.jcarousel, cq.shared and is nowhere to be found neither as dependency nor embed.

Thanks in advance.

View Entire Topic

Avatar

Avatar
Give Back 5
Employee
sunjot16
Employee

Likes

104 likes

Total Posts

164 posts

Correct Reply

50 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 25
Give Back 10
Give Back
View profile

Avatar
Give Back 5
Employee
sunjot16
Employee

Likes

104 likes

Total Posts

164 posts

Correct Reply

50 solutions
Top badges earned
Give Back 5
Give Back 3
Give Back 25
Give Back 10
Give Back
View profile
sunjot16
Employee

16-07-2020

There are many clientlibs that are not just specific to authoring. They are also related to how your content/components appear on the UI, lazy loading of assets, etc. If you remove any clientlibs that might be required, it would mess up your UI. You would have to replicate them from author and even rebuilt clientlibs, if needed.

Just do a thorough testing when you perform the cleanup, such that you don't miss anything that could lead to potential issues in the future.