Client Libraries JavaScript Page Head Not Loading into Publisher

[FrancescaBueti]

I have configured a Client Library JavaScript Page Head like so:

In author is appears as expected:

In publisher, however, it does not appear. All pages and packages are active/published.

Is there anything that could be preventing this from appearing in the publisher instance?

Thanks,

Francesca

[Mali001]

francesca​ You might have to reference using /etc.clientlibs but before that you need to configure "Client Library Folder and Using the Proxy Client Libraries Servlet" - Please check Using Client-Side Libraries - read section "Locating Client Library Folder and Using the Proxy Client Libraries Servlet"

[Ravi_Pampana · Accepted solution]

If your clientlibs files are under /apps (which is recommended by adobe from AEM 6.4 onwards) you need to add "allowProxy" property so that clientlibs will be loaded via etc.clientlibs

jcr:primaryType="cq:ClientLibraryFolder"

allowProxy="{Boolean}true"

Also, make sure in publisher /etc is having read access for everyone user

From Adobe Documentation:

In order for the client libraries under /apps to be accessible, a proxy servelt is used. The ACLs are still enforced on the client library folder, but the servlet allows for the content to be read via /etc.clientlibs/ if the allowProxy property is set to true.

A static resource can only be accessed via the proxy, if it resides below a resource below the client library folder.

As an example:

• You have a clientlib in /apps/myproject/clientlibs/foo
• You have a static image in /apps/myprojects/clientlibs/foo/resources/icon.png

Then you set the allowProxy property on foo to true.

• You can then request /etc.clientlibs/myprojects/clientlibs/foo.js
• You can then reference the image via /etc.clientlibs/myprojects/clientlibs/foo/resources/icon.png

[smacdonald2008]

As Ravi points out - you should include Clientlibs the correct way - using a script tag does not address best practice.

[FrancescaBueti]

Hi Ravi,

Thank you for your response! I have updated the allowProxy property and the path has been updated accordingly:

However, it is still missing on publish. Though it seems to be able to pull in other clientlibs without issue:

Can you elaborate on how to "make sure in publisher /etc is having read access for everyone user"?

Thanks,

Francesca

[FrancescaBueti]

Hi,

The script tag is generated by referencing the library via the template policy:

Is including libraries at the template-level like so not best practice?

Best,

Francesca

[Ravi_Pampana]

You can add read permission to everyone and anonymous user in publish instance (/etc/designs, /etc/clientlibs) by going to useradmin console and search for below users

Everyone

Anonymous