Skip to main content
abhifoyou
Level 2
Mar 27, 2017 3:39 AM UTC
Solved

Existing Pages created in AEM 6.0 NOT working as expected in AEM 6.1 - PageInfo.json throwing null pointer exception

hi Team,

Our project was running on AEM 6.0 where we created our existing pages. After upgrading to AEM 6.1, we installed the existing pages using package manager. All our components/templates/clientlibs got installed perfectly. 

But when we try to open the new page and drag/drop new components from sidekick, first of all no components are showing in sidekick and when we try to add using design mode, page gives internal server error in console. Please suggest.

http://localhost:4502/libs/wcm/core/content/pageinfo.json - > throws null pointer exception

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    abhifoyouAccepted solution
    Level 2
    Mar 29, 2017 4:17 PM UTC

    Thanks Everyone for replying.

    I got it fixed. It was indeed problem with jcr:content only. It was available in our pages but was missing in the parent pages of the hierarchy. I just added the same and it started working. :)

    View in thread

    7 replies

    kautuk_sahni
    kautuk_sahni
    Level 9
    Mar 27, 2017 8:17 AM UTC

    Can you check if this page has "jcr:content" node?

    ~kautuk

    Translate
    Kautuk Sahni
    sandeepm744005
    sandeepm744005
    Level 5
    Mar 27, 2017 11:36 AM UTC

    Do you have the custom parsys component inside your /apps project ? if yes, then you need to make some corrections in the parsys component code to see the components in the sidekick. There are some changes in Out of box parsys between AEM6.0 and AEM6.1. Can you please verify in geometrixx if same issues exists also there, if not, then you need to make some changes in your template and component code.

    Also, you probably need to make some changes in the components dialog hierarchy to make it compatible working with AEM6.1. Sounds like, good amount of work

    Translate
      abhifoyouAuthor
      Level 2
      Mar 27, 2017 3:59 PM UTC

      Yes Sandeep. It must be our project component/template specific problem because Geometrixx works absolutely fine. Also, we don't have custom parsys inside our project.

      Could you please help with what kind of changes are you suggesting for parsys ? The sidekick is the problem, as components doesnt show up in the sidekick even the component group is checked in design mode. Request your expertise in the same.

      Thanks

      Abhijit

      Translate
      abhifoyouAuthor
      Level 2
      Mar 27, 2017 4:00 PM UTC

      Yes Katuk, we do have a jcr:content node for our pages. The sidekick is the problem, as components doesnt show up in the sidekick even the component group is checked in design mode. 

      Translate
      MC_Stuff
      MC_Stuff
      Level 10
      Mar 28, 2017 1:27 AM UTC

      Hi Abhijit,

      There are souple of scenario encountered this issu. Basically The error indicates there is orphaned user exists OR some of resource components not started Or Content had wrong cloud config. My advise would be to engage with official support team.  If you have patience & able to share below information. Community can try to help you. Please send

      1) Output of view-source:http://host:port/system/console/components

      2)  Output of all log files.

      3)   Download the package and send output as mentioned in https://github.com/Adobe-Consulting-Services/acs-aem-tools/issues/177

      Thanks,

      Translate
      abhifoyouAuthorAccepted solution
      Level 2
      Mar 29, 2017 4:17 PM UTC

      Thanks Everyone for replying.

      I got it fixed. It was indeed problem with jcr:content only. It was available in our pages but was missing in the parent pages of the hierarchy. I just added the same and it started working. :)

      Translate
      kautuk_sahni
      kautuk_sahni
      Level 9
      Mar 30, 2017 6:12 AM UTC

      Abhijit paul wrote...

      Thanks Everyone for replying.

      I got it fixed. It was indeed problem with jcr:content only. It was available in our pages but was missing in the parent pages of the hierarchy. I just added the same and it started working. :)

       

      Thanks a lot for sharing the solution with the community.

      ~kautuk

      Translate
      Kautuk Sahni
      Terms & ConditionsAccessibility statement

      Loading footer...