Missing jcr:content node on the page. | Community
Skip to main content
Nandujee
Level 3
October 30, 2017
Solved

Missing jcr:content node on the page.

  • October 30, 2017
  • 6 replies
  • 7512 views

Hello guys,

I would like to understand about the "jcr: content" node. The node creates on the page creation. Would you tell me, when the node will be deleted?

I can see the page with "jcr:content" node on Author instance but the same page does not contain "jcr:content" node on Publisher instance. The page is deactivated on Author.

Please help me to understand about this.

Thanks

Nanda

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 AnkurAhlawat-1

Hi Nanda,

jcr:content node is created at time of page creation. Pages in both author and publish should have jcr:content node. This node is deleted when we delete the respective page.

If we deactivate any page from author -  respective page should be deleted from publish.

Verified mentioned result in aem 6.2

6 replies

AnkurAhlawat-1
AnkurAhlawat-1Accepted solution
Level 6
October 30, 2017

Hi Nanda,

jcr:content node is created at time of page creation. Pages in both author and publish should have jcr:content node. This node is deleted when we delete the respective page.

If we deactivate any page from author -  respective page should be deleted from publish.

Verified mentioned result in aem 6.2

premchandr61956
Level 2
October 30, 2017

Hi Nandu,

We are also facing the same issue in 6.3 instance. In which instance or you facing the issue.  And are you facing this issue after an upgrade or fresh instance?.

Thanks,

Prem

BrijeshYadav
Level 5
October 30, 2017

Hi Nandu,
I would like to share one scenario where jce:content node doesn't created in publish.

Suppose you have created two pages first page called parentPage and second page created under parentPage called childPage. Now only childPage has been activated ..in this case dummy parentPage node will created in publish without any jcr:content along with complete childPage.

/Brijesh Yadav

viveksachdeva
Community Advisor
Community Advisor
October 30, 2017

You should not publish a child page if parent parent doesnt exist on publish. It creates issues. The one that you mentioned regarding jcr:content node not being created, it causes problems. I have seen it in 5.6 but I think it could be same in 6.x as well.

Take a look at KeEp cAlm & just cOdE it! : New Page/Site or Page Properties for a page disabled from siteadmin?  for details...

Nandujee
NandujeeAuthor
Level 3
October 30, 2017

Yes, I agree with you, the page will be deleted from the publisher.

In my case, page still exists on the publisher after deactivation. But the jcr:content node is not present for the page. I can see the page in CRXDE  but without jcr:content.

I want to understand, how can it be possible?

Level 2
February 8, 2019

I don't understand why AEM doesn't suggest the parent publication in the same way that page referecenes.

If a page without jcr:content have no sense, maybe AEM should public the parent or nothing in this case.