ACS Commons Upgrade | Community
Skip to main content
S
SachithaKo2
New Participant
January 3, 2025
Solved

ACS Commons Upgrade

  • January 3, 2025
  • 3 replies
  • 689 views

We are using AEM as a cloud service version 6.5.19.0 and ACS AEM Commons version 5.0.2. We are facing issues with the Dispatcher flush feature and the MD5 hash that is getting added to the client libraries after deploying JS or CSS changes. To fix both issues, we are planning to upgrade the ACS Commons version to 6.10.0. Can anyone help me with the best considerations to avoid any potential issues? Also, if you have faced any issues post-upgrade, please share your experience.

Best answer by Raja_Reddy

Hi @sachithako2 
try ACS Commons version to 6.0.0. it will work for Dispatcher flush feature as well.
https://github.com/Adobe-Consulting-Services/acs-aem-commons/releases?page=3 

3 replies

kautuk_sahni
kautuk_sahni
Employee
March 5, 2025

@sachithako2 Did you find the suggestions helpful? Please let us know if you need more information. If a response worked, kindly mark it as correct for posterity; alternatively, if you found a solution yourself, we’d appreciate it if you could share it with the community. Thank you!

Kautuk Sahni
Raja_Reddy
Raja_ReddyAccepted solution
New Participant
January 3, 2025

Hi @sachithako2 
try ACS Commons version to 6.0.0. it will work for Dispatcher flush feature as well.
https://github.com/Adobe-Consulting-Services/acs-aem-commons/releases?page=3 

    SreenivasBr
    SreenivasBr
    New Participant
    January 3, 2025

    To reduce the impact while upgrading, do the following : 

    1. List down the ACS Commons features which are used in your project.
    2. Make sure the cloud package of ACS Commons is used.
    3. Take a backup of environment before installing, so that it can be restored in case of any major issues.
    4. Validate the features in lower environments (dev), once tested, upgrade in higher environments (stage, prod).
    5. If features are deprecated or not working, you might have to consider another custom solution.

    I have faced problem with versioned clientlibs. I think there is a OOTB feature from AEM which can be used for versioning - https://experienceleague.adobe.com/en/docs/experience-manager-cloud-service/content/implementing/content-delivery/caching#content-consistency

     

     

      Terms & ConditionsAccessibility statement

      Loading footer...