xtype: tags issue after upgrading to AEM 6.4 | Community
Skip to main content
P
puniths34934369
Level 2
April 2, 2019
Solved

xtype: tags issue after upgrading to AEM 6.4

  • April 2, 2019
  • 3 replies
  • 2856 views

Hi,

We have upgraded our instance to AEM 6.4.3, After the upgrade, any component which has more than 1 xtype:tags throws the below exception in the console.

Anyone encountered it? Attached the screenshot of the error

    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 vish.dhaliwal

    Hello,

    This is a known issue, with an internal id-> CQ-4262680. The fix for this issue will be part of the upcoming release AEM 6.4.4 which is going to be released tomorrow.

    Regards,

    Vishu

    3 replies

    U
    Adobe Employee
    user05162Adobe Employee
    Adobe Employee
    April 3, 2019

    Punith,

    Do you see any functional impact by this exception?

    Also, xtype was used classic UI which has been deprecated since AEM 6.3. Going forward, you should be looking at upgrading the components to use coralUI

    V
    Adobe Employee
    vish.dhaliwalAdobe EmployeeAccepted solution
    Adobe Employee
    April 3, 2019

    Hello,

    This is a known issue, with an internal id-> CQ-4262680. The fix for this issue will be part of the upcoming release AEM 6.4.4 which is going to be released tomorrow.

    Regards,

    Vishu

      A
      Adobe Employee
      aemmarc2Adobe Employee
      Adobe Employee
      April 3, 2019

      Vish.dhaliwal​'s answer is correct.

      This is a bug specific to 6.4.3 that is fixed in 6.4.4

      NOTE : post install of 6.4.4 you may want to purge the clientlib and sightly cache's from the filesystem.

      Under \crx-quickstart\launchpad\felix grep for "Outputcache" -- delete the contents of this folder. -- this is the client library cache

      Under \crx-quickstart\launchpad\felix grep for "Classes"  -- delete the contents of this folder. -- this is the sightly cache

        Terms & ConditionsAccessibility statement

        Loading footer...