Page manager return null for mapped page with Sling Mapping | Community
Skip to main content
March 14, 2019
Solved

Page manager return null for mapped page with Sling Mapping

  • March 14, 2019
  • 3 replies
  • 2790 views

Hi All,

I am using Sling Mapping (configurations are located under /etc/map) for mapping the resources , e.g. /content/path/en should get page /content/path_real/en.

When I try to get resource via resourceResolver.getResource("/content/path/en") it works correctly and return the resource under path /content/path_real/en.

But when I try to get page via pageManger.getPage(""/content/path/en") it returns null.

Is there any way to configure pageManager so they also use sling mapping configuration from /etc/map folder?

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 joerghoh

The pagemanager does accept only repository paths, but not request paths (which can be mapped to resource paths).

Jörg

3 replies

Prince_Shivhare
Community Advisor
Community Advisor
March 14, 2019

If the resource at that path does not exist or is not adaptable to Page, null is returned.

are you doing like this?

PageManager pageManager = resolver.adaptTo(PageManager.class);

  if (pageManager != null) {

  Page page = pageManager.getPage(path);

or something like --

PageManager pageManager = resource.getResourceResolver().adaptTo(PageManager.class);

Page rootPage = pageManager.getPage(pagePath);

~ Prince

joerghoh
Adobe Employee
joerghohAdobe EmployeeAccepted solution
Adobe Employee
March 14, 2019

The pagemanager does accept only repository paths, but not request paths (which can be mapped to resource paths).

Jörg

Gaurav-Behl
Level 10
March 14, 2019

As Jörg mentioned above,  get the resource first using resourceResolver.getResource("/content/path/en")

then use pageManger.getPage(resource.getPath())