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

SOLVED

AEM - Implementation of Versioning for Clientlibs and CSS

aem_dev9
Level 1
Level 1

Hello AEM Guru,

 

We have many versioning documents available but still have few queries.

 

I am new to AEM and have to implement  clientlibs versioning as with every deployment client libs are not getting updated in the normal browser even after flushing the dispatcher cache and CDN cache. Tried to implement as suggested by many.

Facing below few issues :

1. I am tried to implemnet this via crxde in local . if we want to do it via code how to do that . /apps/<project folder/config/rewriter/ - should a create an xml file and copy paste this code :

<?xml version="1.0" encoding="UTF-8"?>

<jcr:root xmlns:sling="http://sling.apache.org/jcr/sling/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0"

jcr:primaryType="sling:Folder"

contentTypes="[text/html]"

enabled="{Boolean}true"

generatorType="htmlparser"

order="{Long}1"

serializerType="htmlwriter"

transformerTypes="[linkchecker,versioned-clientlibs]"/>

This is required, as in our higher environment we don't have access to CRXDE console.  

 

#2 - In my local, i did the changes via  crxde and save all.  but still not seeing configuration in sling rewrite. even after restarting the instance.


Any help would be highly appreciated

1 Accepted Solution
Arun_Patidar
Correct answer by
Community Advisor
Community Advisor
3 Replies
Arun_Patidar
Correct answer by
Community Advisor
Community Advisor
JAWillis
Level 2
Level 2
Good day, so I have also followed the steps in the above link, I can see the rewrite in the sling rewrite status, but when looking at the code of a webpage, the XF css and JS have the versioning but not any of the clientlib css or js, could anybody perhaps guide me in what could be wrong? Thank you
Arun_Patidar
Community Advisor
Community Advisor
which version of AEM are you using, there was an issue with AEM 6.5.7 with clientlibs