Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

AEM Pattern Detector: content.area.violation

Avatar

Avatar
Level 1
jag01
Level 1

Likes

0 likes

Total Posts

4 posts

Correct Reply

0 solutions
View profile

Avatar
Level 1
jag01
Level 1

Likes

0 likes

Total Posts

4 posts

Correct Reply

0 solutions
View profile
jag01
Level 1

07-04-2020

Hi All,

 

I'm working on aem 6.3 to 6.5 in place upgrade activity. As part of this, I'm fixing the issues raised by pattern detector. I have found the below issue:

 

jag01_0-1586265442698.png

 

The overlay was done for customization but now the overlay is not allowed for it as mixinType is Internal (granite:InternalArea) - Defines a node as internal. Nodes classified as internal cannot be overlaid, inherited, or used directly. These nodes are meant only for internal functionality of AEM

 

We require the customization, so is there any way to resolve it.

 

Thanks

 

 

 

how to

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Validate 1
MVP
Theo_Pendle
MVP

Likes

236 likes

Total Posts

251 posts

Correct Reply

105 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 10
Ignite 1
View profile

Avatar
Validate 1
MVP
Theo_Pendle
MVP

Likes

236 likes

Total Posts

251 posts

Correct Reply

105 solutions
Top badges earned
Validate 1
Ignite 5
Ignite 3
Ignite 10
Ignite 1
View profile
Theo_Pendle
MVP

07-04-2020

A content area violation (CAV) is detected because you are currently overriding or overlaying a node which is (or will be after the upgrade) in a "restricted area". You can read more about content areas here: https://docs.adobe.com/content/help/en/experience-manager-64/deploying/upgrading/sustainable-upgrade...

To make a comparison: overlaying a node that is in a granite:internalArea is a bit like trying to extend a class which is marked as final in Java (ie: not allowed!).

You will have to do remove the offending node.

Based on your previous questions, I suspect that this too is a result of an outdated ACS Commons package being installed on your instance.

Answers (0)