How to work with deprecated acs-commons tag libs | Community
Skip to main content
CT1012
Level 4
September 7, 2017
Solved

How to work with deprecated acs-commons tag libs

  • September 7, 2017
  • 8 replies
  • 1941 views

We are upgrading from 5.6.1 to 6.3

Went through some of the docs and found acs-commons deprecated tag libs. Tag libs used in our project are  wcmmode, widgets and xss listed under global.jsp

Most of the docs over internet shown usage of HTL tags. If mandatory to use HTL tags, how to work with Sightly for classic UI components since we are using only classic UI. Suggest me the changes for global.jsp and tags.

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

Please use Touch UI and HTL. this is now recommended and also in upcoming versions possibly classic UI will not be there.

so better if you are moving in 6.3 then please use Touch UI.

Regards,
Prince

8 replies

smacdonald2008
Level 10
September 7, 2017

If you are upgrading to AEM 6.3 - recommended approach is to change you components to HTL and Touch UI dialogs.  At some point Classic **may** disappear.

Prince_Shivhare
Community Advisor
Prince_ShivhareCommunity AdvisorAccepted solution
Community Advisor
September 7, 2017

Please use Touch UI and HTL. this is now recommended and also in upcoming versions possibly classic UI will not be there.

so better if you are moving in 6.3 then please use Touch UI.

Regards,
Prince

CT1012
CT1012Author
Level 4
September 7, 2017

They need classic to maintain the crew who normally author,also they want to finish in a very short time time since it is a small project.  This will be the final version they're using from AEM.

Conversion of components to HTL is a big task now, so please help me with alternatives to tag libs.

smacdonald2008
Level 10
September 7, 2017

See: WCMMode Tags & Functions

However - if you really want to  - you can try using them in AEM 6.3. If you run into issues - i am not sure it will be supported.

Deprecated means we encourage you not to use them (as they will be gone in a future version). We recommend using HTL instead.

CT1012
CT1012Author
Level 4
September 7, 2017

Thank you

-I'm getting the below error

Caused by: org.apache.sling.scripting.jsp.jasper.JasperException: /apps/XXXX/components/content/top-navigation/top-navigation.jsp(14,0) The attribute prefix widgets does not correspond to any imported tag library

-14th line of jsp has

<c:set var="links" value="${widgets:getMultiFieldPanelValues(resource, loginVar)}"/>

smacdonald2008
Level 10
September 7, 2017

What version of ACS-Commons are you using?

smacdonald2008
Level 10
September 7, 2017

Also - as we stated - using these tag libs is risky - for AEM 6.3 - you should be using Core Components to build an AEM Site -- see:

aem-core-wcm-components/README.md at master · Adobe-Marketing-Cloud/aem-core-wcm-components · GitHub

Ask the AEM Commuity Experts -- Scott's Digital Community: Ask the AEM Community Experts for August 2017

CT1012
CT1012Author
Level 4
September 7, 2017

acs-aem-commons-content-3.8.4.zip

I'm not getting any error on authoring now, thanks for the quick response... Will the tag libs functionality be available if we stay with the current version 3.8.4 of acs-aem-commons ?