AEM Pattern Detector Interpretation | Community
Skip to main content
demobuster
Level 2
Jun 20, 2019 3:39 PM UTC
Solved

AEM Pattern Detector Interpretation

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!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
joerghoh
joerghohAccepted solution
Employee
Sep 26, 2019 11:08 AM UTC

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

View reply

12 replies

davidef34326447
Level 3
Oct 15, 2020 5:21 PM UTC
i have tried to "copy and past" the core component "/apps/core/wcm/components/text/v2/text" and the issue is highlighted also on core component "clone":
Translate
davidef34326447
Level 3
Oct 5, 2020 11:54 AM UTC
Please, is there an update?
Translate
JakeCham
JakeCham
Level 6
May 18, 2020 9:40 PM UTC
Any updates of this issue.?iam also facing vary same issue while upgrading to 6.5
Translate
joerghoh
joerghohAccepted solution
Employee
Sep 26, 2019 11:08 AM UTC

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

Translate
    pjpop
    New Participant
    Sep 25, 2019 8:28 PM UTC

    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!

    Translate
      nupur_k
      Level 2
      Sep 17, 2019 6:04 AM UTC

      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 ,

      Translate
        vish.dhaliwal
        Employee
        Aug 22, 2019 4:04 PM UTC

        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

        Translate
          Sabarishreddy-1
          Level 2
          Jun 11, 2020 10:12 PM UTC

          Can you share the Link to the bug? not sure where to look for status

          Translate
          Anonymous
          Aug 22, 2019 9:11 AM UTC

          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.

          Translate
            demobusterAuthor
            Level 2
            Jun 26, 2019 4:41 PM UTC

            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

            Translate
              joerghoh
              joerghoh
              Employee
              Jun 26, 2019 3:26 PM UTC

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

              Jörg

              Translate
                Show more replies
                Terms & ConditionsAccessibility statement

                Loading footer...