Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn More

View all

Sign in to view all badges

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

Avatar

Avatar
Validate 1
Level 2
JitPaul
Level 2

Likes

4 likes

Total Posts

11 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile

Avatar
Validate 1
Level 2
JitPaul
Level 2

Likes

4 likes

Total Posts

11 posts

Correct Reply

1 solution
Top badges earned
Validate 1
Boost 3
Boost 1
Affirm 1
View profile
JitPaul
Level 2

26-03-2017

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

View Entire Topic

Avatar

Avatar
Validate 10
Level 4
sandeepm744005
Level 4

Likes

19 likes

Total Posts

127 posts

Correct Reply

13 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Validate 10
Level 4
sandeepm744005
Level 4

Likes

19 likes

Total Posts

127 posts

Correct Reply

13 solutions
Top badges earned
Validate 10
Validate 1
Ignite 5
Ignite 3
Ignite 1
View profile
sandeepm744005
Level 4

27-03-2017

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