Hi All,
When we publish the page, the cq:lastReplicated property is not updated in the published instance.
While the cq:lastModified property is updated, the cq:lastReplicated property is not.
What would be the issue here, and can you help me if anyone comes across this issue?
Is it possible to show the cq:lastReplicated node data in a published instance?
Thanks in advance.
Kaibalya
Solved! Go to Solution.
Views
Replies
Total Likes
hi publish environment does not have cq:lastReplicated property. The equivalent property on a page that you would get to see on publish instance is, jcr:created. This property gets updated every time a page is published. So, technically jcr:created property's value in publish instance and cq:lastReplicated value in author instance will almost always identical.
hi publish environment does not have cq:lastReplicated property. The equivalent property on a page that you would get to see on publish instance is, jcr:created. This property gets updated every time a page is published. So, technically jcr:created property's value in publish instance and cq:lastReplicated value in author instance will almost always identical.
@Kaibalya_123 cq:lastReplicated property is not carried over to publish by design. In order to carry it over, disable the below component in the author instance:
com.day.cq.replication.impl.ReplicationPropertiesFilterFactory
Note: On Publisher this property is redundant, cq:lastModified on publisher captures the same info as cq:lastReplicated.
When a page is published from Author -> Publisher, the publisher see's the resource as a new item added. You should be okay to use the currentPage.jcr:created as this date can represent the last replicated date.
But however, just as a experiment for yourself, when looking at the Author, the jcr:created is the actual creation date of when the page was created (this date will neverchange), and you can actually find the cq:lastReplicated, as this will be the actual lastReplication date.
Views
Likes
Replies