Node structure for page a under /tmp/versionhistory is not similar to the node structure under /content/we-retail | Community
Skip to main content
H
H_Malhotra
Level 2
March 10, 2022
Solved

Node structure for page a under /tmp/versionhistory is not similar to the node structure under /content/we-retail

  • March 10, 2022
  • 1 reply
  • 1535 views

Hi All,

I'm trying to use the page versionhistory functionality available in AEM. However, when I'm creating the page version of a specific page, the node structure of the parent nodes is not entirely getting created under the /tmp/versionhistory. 
For instance: I'm creating the version of page under /content/we-retail/us/en which is having the following node structure:

The node structure created under the temp/versionhistory node is as follows:

The image node available under content/we-retail/jcr:content is not available in the similar hierarchy under /tmp/versionhistory node structure.

Could you please let me know how can I generate the same node strucute 

 

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 lukasz-m

Hi @h_malhotra, I think you are looking for version under incorrect location. The version itself is stored under /jcr:system/jcr:versionStorage - you can navigate to the versions of specific page by clicking on value of jcr:versionHistory property. There you will find complete copy that has been created as a version.

/tmp/versionhistory is used by version comparison functionality. Which in general allows authors to compare visual/content differences between 2 versions. You are not seeing this image node because it looks it is not needed for comparison - as far as I know it stores image set under page properties, and comparison tool is not allowing you to show changes from page properties.

If you want to use AEM versioning functionality, you should use versions kept under /jcr:system/jcr:versionStorage - and Jcr Version Manger API to do any operation related to versions from the code.

 

1 reply

lukasz-m
Community Advisor
lukasz-mCommunity AdvisorAccepted solution
Community Advisor
March 10, 2022

Hi @h_malhotra, I think you are looking for version under incorrect location. The version itself is stored under /jcr:system/jcr:versionStorage - you can navigate to the versions of specific page by clicking on value of jcr:versionHistory property. There you will find complete copy that has been created as a version.

/tmp/versionhistory is used by version comparison functionality. Which in general allows authors to compare visual/content differences between 2 versions. You are not seeing this image node because it looks it is not needed for comparison - as far as I know it stores image set under page properties, and comparison tool is not allowing you to show changes from page properties.

If you want to use AEM versioning functionality, you should use versions kept under /jcr:system/jcr:versionStorage - and Jcr Version Manger API to do any operation related to versions from the code.

 

    H
    H_MalhotraAuthor
    Level 2
    March 11, 2022

    Thank you for your response @lukasz-m .

    There are a few points that we are having issue with in our project structure, which can be understood by the below reference.
    1. The image node available under content/we-retail/jcr:content is essential to compare/preview the page version created for /content/we-retail/us/en/women. Since the image node is not available under the /tmp/versionhistory node structure, the compare to current and preview functionalities lead to a blank page.
    2. While previewing the page version, a few properties stored under /content/we-retail/us/jcr:content are necessary, which are missing under the /tmp/versionhistory node structure.

    Terms & ConditionsAccessibility statement

    Loading footer...