AEM CaaS | BPA report giving error on RTEs | Community
Skip to main content
VeenaVikraman
Community Advisor
VeenaVikramanCommunity Advisor
Community Advisor
April 29, 2022

AEM CaaS | BPA report giving error on RTEs

  • April 29, 2022
  • 3 replies
  • 1820 views

Hi All

 

    I have been getting below critical issues reported in BPA 

 

 

The content stored at /apps/<project>/cq:dialog/content/items/tabs/items/ep/items/columns/items/column/items/msg 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

 

 

    The field  msg is an RTE and the sling:resourceType is  cq/gui/components/authoring/dialog/richtext which is the Resource Type for rich text. I crossed check with the core components and I could see the same 

 

I am not sure why this is reported as a CRITICAL issue , since we do not have any other type for RTE. Can I safely assume and communicate to client that this is falls positive ?

 

TIA

Veena ✌

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

3 replies

VeenaVikraman
Community Advisor
VeenaVikramanCommunity AdvisorAuthor
Community Advisor
April 29, 2022

@kautuk_sahni Is it possible to check this with someone from product team ? 

    kautuk_sahni
    Community Manager
    kautuk_sahniCommunity Manager
    Community Manager
    May 4, 2022

    Let me get this check...

     

    Kautuk Sahni
    VeenaVikraman
    Community Advisor
    VeenaVikramanCommunity AdvisorAuthor
    Community Advisor
    April 29, 2022

    Just an update on this. I copied the v2 version of text component from core components to my project code and ran the BPA again and this is reported as a CRITICAL issue for that component too.

      Ravi_Pampana
      Community Advisor
      Ravi_PampanaCommunity Advisor
      Community Advisor
      April 29, 2022

      Hi,

       

      May be the node name is causing the issue (msg), try to change it. Anyway the issue is reported in author which will be accessible only with valid credentials and permissions, we can ignore the issue.

        arunpatidar
        Community Advisor
        arunpatidarCommunity Advisor
        Community Advisor
        April 29, 2022

        Agree, could be issue with node name.  know if you have 'config' nodename for the dialog field, there is an issue. So better to rename to check and confirm.

        Arun Patidar
          N
          NehaMa
          Level 4
          November 23, 2022

          hi @veenavikraman @kautuk_sahni - were we able to confirm on same , is it critical issue

            Terms & ConditionsAccessibility statement

            Loading footer...