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 Interpretation

Avatar

Avatar
Validate 10
Level 2
Sergei_P2018
Level 2

Likes

4 likes

Total Posts

23 posts

Correct Reply

1 solution
Top badges earned
Validate 10
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 10
Level 2
Sergei_P2018
Level 2

Likes

4 likes

Total Posts

23 posts

Correct Reply

1 solution
Top badges earned
Validate 10
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
Sergei_P2018
Level 2

20-06-2019

Hi all

We're analyzing the output of the Pattern Detector and some of the violations seems strange.

1. Non-Backwards Compatible Changes

For instance, we getting:

The content stored at /apps/<...>/cq:dialog/content/items/section3/items/column/items/details-group/items/details by including (sling:resourceType) the JCR path at /libs/cq/gui/components/authoring/dialog/richtext might be incompatible after update and might need some adaption

We would like to learn more about the severity of this issue, like what type of change is expected? Is there a backward compatible alternative for richtext, for instance?

2. Content Area Violation

For instance, we getting:

The content stored at /apps/<...> by overriding (sling:superResourceType) the JCR path at /libs/cq/workflow/components/model/process might be incompatible after update and might need some adaption

However /libs/cq/workflow/components/model/processis is explicitly marked as granite:PublicArea which is safe for that type of actions.

If anyone has answers, please share.

Thanks in advance!

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,133 likes

Total Posts

3,161 posts

Correct Reply

1,079 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,133 likes

Total Posts

3,161 posts

Correct Reply

1,079 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
Employee

26-09-2019

If the documentation does not provide actionable information how you can handle these, I would recommend you to open a support ticket and ask for advice.

Unfortunately I don't have first-hand experience with it yet, so I cannot help you in that area 😕

Jörg

Answers (7)

Answers (7)

Avatar

Avatar
Give Back 50
Employee
Vish_dhaliwal
Employee

Likes

189 likes

Total Posts

356 posts

Correct Reply

123 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile

Avatar
Give Back 50
Employee
Vish_dhaliwal
Employee

Likes

189 likes

Total Posts

356 posts

Correct Reply

123 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 10
View profile
Vish_dhaliwal
Employee

22-08-2019

Hello,

There is a known bug in pattern detector : CQ-4269181.

The warnings like [1] seems to be the result of this bug. You can safely ignore these warnings/errors until this issue is fixed.

[1] The content stored at /apps/<...>/cq:dialog/content/items/section3/items/column/items/details-group/items/detai ls by including (sling:resourceType) the JCR path at /libs/cq/gui/components/authoring/dialog/richtext might be incompatible after update and might need some adaption

Regards,

Vishu

Avatar

Avatar
Boost 1
Level 1
paulj76473728
Level 1

Like

1 like

Total Posts

1 post

Correct Reply

0 solutions
Top badges earned
Boost 1
View profile

Avatar
Boost 1
Level 1
paulj76473728
Level 1

Like

1 like

Total Posts

1 post

Correct Reply

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

25-09-2019

Can you please provide more details about this bug and an ETA for fixing it? We are working through an upgrade to 6.5 right now and have over 40 of these errors that the pattern detector is warning us about. If I'm going to ignore these errors, I really need more concrete details as to why this is safe to do, so that I can explain the decision to project stakeholders. Thank you!

Avatar

Avatar
Validate 1
Level 2
nupur_k
Level 2

Likes

3 likes

Total Posts

12 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Applaud 5
View profile

Avatar
Validate 1
Level 2
nupur_k
Level 2

Likes

3 likes

Total Posts

12 posts

Correct Reply

0 solutions
Top badges earned
Validate 1
Boost 3
Boost 1
Applaud 5
View profile
nupur_k
Level 2

16-09-2019

Hi,

Can you help me on these issues what needs to be done to fix all these violations. 1 & 2. Will these harm working of the components as backward compatibility support is already there. And most of components build on coral 2, and coral 2 is still supported in 6.5

these similar ones reportedly appear in PD report for so many components in migration from 6.2 to 6.5 ,

Avatar

Avatar
Boost 1
Level 1
rajasekharb2226
Level 1

Like

1 like

Total Posts

1 post

Correct Reply

0 solutions
Top badges earned
Boost 1
View profile

Avatar
Boost 1
Level 1
rajasekharb2226
Level 1

Like

1 like

Total Posts

1 post

Correct Reply

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

22-08-2019

Hi,

1. Non-Backwards Compatible Changes

For instance, we getting:

The content stored at /apps/<...>/cq:dialog/content/items/section3/items/column/items/details-group/items/detai ls by including (sling:resourceType) the JCR path at /libs/cq/gui/components/authoring/dialog/richtext might be incompatible after update and might need some adaption

kindly help me out on this issue as im getting these results for every component.

Avatar

Avatar
Validate 10
Level 2
Sergei_P2018
Level 2

Likes

4 likes

Total Posts

23 posts

Correct Reply

1 solution
Top badges earned
Validate 10
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 10
Level 2
Sergei_P2018
Level 2

Likes

4 likes

Total Posts

23 posts

Correct Reply

1 solution
Top badges earned
Validate 10
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
Sergei_P2018
Level 2

26-06-2019

Hi Joerg Hoh

We use pd-all-aem65-0.10 package and the upgrade is taking place from 6.4.3 to 6.5.0

Avatar

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,133 likes

Total Posts

3,161 posts

Correct Reply

1,079 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,133 likes

Total Posts

3,161 posts

Correct Reply

1,079 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
Employee

26-06-2019

what version of the pattern detector ruleset are you using? What version are you coming from?

Jörg

Avatar

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,198 likes

Total Posts

6,369 posts

Correct Reply

1,147 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile

Avatar
Establish
Community Manager
kautuk_sahni
Community Manager

Likes

1,198 likes

Total Posts

6,369 posts

Correct Reply

1,147 solutions
Top badges earned
Establish
Coach
Originator
Contributor 2
Contributor
View profile
kautuk_sahni
Community Manager

26-06-2019

Joerg Hoh​ Need you help here.

-kautuk