xtype: tags issue after upgrading to AEM 6.4

Avatar

Avatar

puniths34934369

Avatar

puniths34934369

puniths34934369

02-04-2019

xtype_error.PNGHi,

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

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Vish_dhaliwal

Employee

Avatar

Vish_dhaliwal

Employee

Vish_dhaliwal
Employee

03-04-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

Answers (2)

Answers (2)

Avatar

Avatar

aemmarc

Employee

Avatar

aemmarc

Employee

aemmarc
Employee

03-04-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

Avatar

Avatar

jbrar

Employee

Avatar

jbrar

Employee

jbrar
Employee

02-04-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