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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

ClientLibs not working | Migration AEM6.0 to AEM6.4

_SumitSinghal
Level 4
Level 4

Hi Team,

We are upgrading our environment from AEM6.0 to AEM6.4 while upgrading we wanted the clientLibs to be under /etc/design instead of new approach where Adobe recommends to keep in /apps/settings/wcm/design .

We are able to make clientlibs work fine if they are kept under /apps but not able to make it work if kept under /etc on dispatcher. As on dispatcher it looks for the path /etc.clientlibs and there it couldn't find the client libs.

Refer this link : Re: AEM 6.3 Proxy ClientLibs didn't work via dispatcher to publisher.   (But it didn't work)

Can anyone help me to make clientlibs work if kept under /etc/design on dispatcher.

Thank you

10 Replies
_SumitSinghal
Level 4
Level 4

Hi Ashish,

Thank you for the info.

It would be good if you can share more info from AEM6.4 as it might be working on AEM6.3 .

Thank you

_SumitSinghal
Level 4
Level 4

Hi Team,

I am still looking out for the solution where in I want to use the clientlibs under /etc instead of /apps which is the new approach in AEM6.4 .

Is AEM6.4 is backward compatible ? If yes then I think it should support clientlibs residing under /etc as well.

Can anyone help me out ?

Thanks

Jörg_Hoh
Employee
Employee

AEM 6.4 is backward compatible in a way, that clientlibs below /etc are still possible and allowed, although you are encouraged to move.

smacdonald2008
Level 10
Level 10

As Joerg mentions - its now considered best practice to move the location of clientlibs. Why are you keeping it under /etc when Adobe recommends moving from /etc?

smacdonald2008
Level 10
Level 10

For community members new to AEM 6.4 and want to know best practice for using ClientLibs - its not keeping it under /etc. To learn best practices - read this -- Getting Started with AEM Sites Part 3 - Client-Side Libraries and Responsive Grid

Jörg_Hoh
Employee
Employee

smacdonald2008​ I totally understood, when projects put a higher priority to an AEM 6.4 upgrade than to any change to repo structure if the old structure is still supported. I would also strongly suggest to postpone all of these recommended repo structure changes until you are on AEM 6.4. If you are on 6.4 then it's time to do it. But first make sure that you arrive safely there 🙂

Jörg

_SumitSinghal
Level 4
Level 4

Hi ,

The main reason behind keeping the js/css under /etc is in our code base on JSPs the path of js/css files is directly from /etc . If we move to /apps we need to change in all the JSP files.

Another reason is dispatcher is not reading the files from /etc/design as it reads from /apps with the new approach in AEM6.4 .

Thank you for such a quick response

_SumitSinghal
Level 4
Level 4

Hi ,

The main reason behind keeping the js/css under /etc is in our code base on JSPs the path of js/css files is directly from /etc . If we move to /apps we need to change in all the JSP files.

Another reason is dispatcher is not reading the files from /etc/design as it reads from /apps with the new approach in AEM6.4 .

Thank you for such a quick response

Jörg_Hoh
Employee
Employee

Hi,

with the clientlib mechanism in place, you shouldn't care about where the files are residing; referencing JS and CSS directly (by path) was never recommended in AEM development. You should use the clientlib tag library.

See Using Client-Side Libraries  for reference.