Ampersand in resource name causing AEM 6.4.8.0 to freeze when dragging in a component | Adobe Higher Education
Skip to main content
June 9, 2020
Beantwortet

Ampersand in resource name causing AEM 6.4.8.0 to freeze when dragging in a component

  • June 9, 2020
  • 2 Antworten
  • 2306 Ansichten

ISSUE

I have encountered an issue where AEM 6.4.8.0 freezes and becomes unresponsive when adding a component into the data sly resource below:

 

 

<sly data-sly-resource="${'q&a-parsys' @ resourceType='wcm/foundation/components/parsys', decorationTagName='div'}"></sly>

 

 

I have narrowed down the cause to the ampersand in 'q&a-parsys' as it works without freezing AEM when changing the code to be 'q-and-a-parsys'.

 

QUESTIONS

Why am I unable to use the ampersand character in this context?

As this previously worked is this a new defect in AEM?

Is it anything to do with this hotfix in 6.4.8.0 AEM assets - Renaming a file using some unsupported special characters like ampersand (&) creates an invalid folder. NPR-29196: Hotfix for CQ-4265037?

Is there a solution other than updating the name in the html file (ideally I'd like to avoid having to update all instances of this resource on Production)?

 

UPDATE

I have done some further investigation and it appears this also wasn't working on AEM 6.4.6 so it's unlikely that it's related to the hotfix in 6.4.8.0

Dieses Thema wurde für Antworten geschlossen.
Beste Antwort von joerghoh

Sounds like a regression, and you should report that to Adobe support asap.

 

What was the servicepack you were using previously and where it worked?

2 Antworten

wsuttonAutor
June 9, 2020
Just seen this hotfix in 6.4.8.0 AEM assets - Renaming a file using some unsupported special characters like ampersand (&) creates an invalid folder. NPR-29196: Hotfix for CQ-4265037 - might this have something to do with the cause?
joerghoh
Adobe Employee
joerghohAdobe EmployeeAntwort
Adobe Employee
June 9, 2020

Sounds like a regression, and you should report that to Adobe support asap.

 

What was the servicepack you were using previously and where it worked?

wsuttonAutor
June 10, 2020
I have done some further investigation it appears this also wasn't working on AEM 6.4.6 so it's unlikely related to the hotfix in 6.4.8.0