AEM Pattern Detector Interpretation

Sergei_P2018

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)

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)

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

paulj76473728

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!

nupur_k

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 ,

rajasekharb2226

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.