AEM Web Console Pattern Detector - non.backwards.compatible.content

Avatar

Avatar
Boost 1
Level 1
jonjonxd1
Level 1

Like

1 like

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile

Avatar
Boost 1
Level 1
jonjonxd1
Level 1

Like

1 like

Total Posts

2 posts

Correct reply

0 solutions
Top badges earned
Boost 1
View profile
jonjonxd1
Level 1

31-03-2020

I'm new to AEM and I'm working in an 6.3 to 6.5 in-place upgrade activity. As part of this, while I'm fixing the issues raised by pattern detector I found the below issue and I'm unable to fix this. Can anyone help me to fix this? 

 

InkedMigratingPatternDetectorError_LI.jpg

This is the possible solution but I don't really know how to do this:

Overlay or reference only Sling components that are backwards compatible

Consider resources needed for adapting changes coming from /libs or bundles after AEM upgrades

Accepted Solutions (0)

Answers (1)

Answers (1)

Avatar

Avatar
Validate 1
MVP
Theo_Pendle
MVP

Likes

238 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

238 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

02-04-2020

Hi Jon, 

 

What this message means is that somewhere in you are referencing a component which works in 6.3 but may no longer work in 6.5.

 

In this specific instance, it looks like your contentpage component overrides wcm/foundation/components/page, which is deprecated in 6.5. The new component to override is wcm/foundation/components/basicpage/v1/basicpage.

 

I am actually also doing a 6.3 -> 6.5 migration at the moment and I highly recommend you migrate towards AEM Core Components which implements many common components (including a Page component) using the latest best practices and a number of great features! Much easier than re-inventing the wheel, and it's backed by Adobe so you don't have to worry about compatibility issues or support 👍