Automatic versioning of clientlibs not working in AEM 6.5.12 | Community
Skip to main content
S
Ss_dev
Level 2
May 18, 2023

Automatic versioning of clientlibs not working in AEM 6.5.12

  • May 18, 2023
  • 3 replies
  • 1653 views

Hi,

 

Current AEM version is - 6.5.12

acs-aem-commons - 4.3.0

 

I configured the clientlib versioning as said in the acs commons site.

 

But the problem is, I have created the node for rewriter under config folder but it doesnt appear in the sling rewriter (http://localhost:4502/system/console/status-slingrewriter), so it indicates configuration was not applied successfully. I even restarted the server but it didnt worked.

 

Please anybody faced this issue.

 

Is it the acs-aem-commons version compatibility issue ?

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

Ritesh_Mittal
Community Advisor and Adobe Champion
Ritesh_MittalCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
May 19, 2023

Hi @ss_dev ,

 

Please check if this old thread helps-

 

https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/acs-commons-clientlibs-versioning-not-working-when-we-deploy/m-p/419417

    S
    Ss_devAuthor
    Level 2
    May 22, 2023

    @ritesh_mittal  Thanks , it is working for me , I created node

    /apps/(myproject)/config/rewriter/versioned-clientlibs  and it is reflecting in the sling rewriter but its not working on JS and CSS concatenation version.

     

    I tried making changes in JS and deployed code, it picked my changes , as I can see in console but when seeing in the Network tabs, the js is without any long string of number but for CSS I can see, a long string of numbers attached.

     

    1. Chances are its picking for CSS and not for JS.

    2. Either its not picking for both and its existing for CSS and not for JS.  (This is the case it seems, I checked on other env, its happening, without making any changes).

     

    Any suggestions on this.

      Shashi_Mulugu
      Community Advisor
      Shashi_MuluguCommunity Advisor
      Community Advisor
      May 21, 2023

      @ss_dev you need to have 2 mandate things to be done, one acs commons osgi configuration and second rewrite node, this should be at exactly 4 level

       

      /apps/(any custom folder)/config/rewriter

        S
        Ss_devAuthor
        Level 2
        May 22, 2023

        Thanks @shashi_mulugu  Its picking my config but the issue is testing. Even after making changes, its just not reflecting in js version but on the css version.

         

        So I am not sure if the config had any impact on the clientlibs.

         

          fmateen
          fmateen
          Level 2
          January 24, 2025

          I followed

          https://adobe-consulting-services.github.io/acs-aem-commons/features/versioned-clientlibs/index.html

          and used Rewrite Configuration Node Solution

          I am using 6.5.22 it worked only after changing the value of the order property to a higher number for example 1001. It was not working when the value of the order property was 1

           

          Try changing the value of order property because it seems the bundle is not picking the config with lower value.  

          Terms & ConditionsAccessibility statement

          Loading footer...