Anomaly found on CMS for both the data not showing correctly | Community
Skip to main content
S
Sai1278
Level 3
April 4, 2024
Solved

Anomaly found on CMS for both the data not showing correctly

  • April 4, 2024
  • 4 replies
  • 2533 views

Hi Adobe Family,
we report an anomaly found on AEM for both the "xyz project" and "zyx project" nodes (both dev and qa). When we select the content list view, we display the info columns for each node with the wrong header, therefore not corresponding to the data in the column. For example, in the "Published" column we display the content templates, in the "Template" column there is no information, in the "Modified" column there is information about the publication instead of the modification. 

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

Hi @sai1278 

Please compare the following paths:

  1. /apps/wcm/core/content/common/availablecolumns
  2. /libs/wcm/core/content/common/availablecolumns

Are the data and nodes the same, or are there any extra nodes? This might be the issue. I think there are some extra nodes in the /apps/wcm/core/content/common/availablecolumns section.

4 replies

EstebanBustamante
Community Advisor and Adobe Champion
EstebanBustamanteCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
April 4, 2024

Hi,

 

First, let's determine if this issue is specific to projects "xyz" and "zyx." If it is, then the problem might be limited to those projects. However, if the issue persists across the entire instance, it could indicate a broader problem with the entire system.

Have you recently upgraded AEM or performed any significant operations? Changes like these could potentially affect the functionality of the platform.

Additionally, I recommend checking the browser console and error logs for any relevant error messages. This information can provide valuable insights into what might be causing the issue. Any additional details you can provide would be greatly appreciated.

 

Hope this helps

Esteban Bustamante
    S
    Sai1278Author
    Level 3
    April 5, 2024

    Hi @estebanbustamante 
    It has come to our attention that all environments are experiencing a particular issue, despite no recent updates being made to Adobe Experience Manager (AEM). Surprisingly, there are no console errors being reported.

      EstebanBustamante
      Community Advisor and Adobe Champion
      EstebanBustamanteCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      April 5, 2024

      Hi, 

      Did you try to replicate the issue without your codebase? To make sure is AEM related and not your custom code?

      I could not reproduce the issue (Using AEM6.5.16)

       

      Esteban Bustamante
        S
        Sai1278Author
        Level 3
        April 5, 2024

        Please give me some guidance
        @arunpatidar Jörg_Hoh
        aanchal-sikka
        lukasz-m
        SureshDhulipudi

        Raja_Reddy

          arunpatidar
          Community Advisor
          arunpatidarCommunity Advisor
          Community Advisor
          April 5, 2024

          Hi @sai1278 
          What AEM version are you using?

          Can you please also try in vanilla instance without your code?

          Arun Patidar
            S
            Sai1278Author
            Level 3
            April 5, 2024

            Hi @arunpatidar 
            The AEM version was 6.5

              arunpatidar
              Community Advisor
              arunpatidarCommunity Advisor
              Community Advisor
              April 5, 2024

              Hi @sai1278 

              I am on AEM 6.5.16

              I can see all the values as expected.

               

               

              did you tried in vanilla instance with we.retail code?

              Arun Patidar
                Raja_Reddy
                Community Advisor
                Raja_ReddyCommunity AdvisorAccepted solution
                Community Advisor
                April 8, 2024

                Hi @sai1278 

                Please compare the following paths:

                1. /apps/wcm/core/content/common/availablecolumns
                2. /libs/wcm/core/content/common/availablecolumns

                Are the data and nodes the same, or are there any extra nodes? This might be the issue. I think there are some extra nodes in the /apps/wcm/core/content/common/availablecolumns section.

                  S
                  Sai1278Author
                  Level 3
                  April 8, 2024

                  Hi @raja_reddy 
                  Thanks for your support. I understand now. I have removed the extra node, and it is displaying correctly.

                   

                    Terms & ConditionsAccessibility statement

                    Loading footer...