Hi Everyone,
We have migrated from AEM 5.6 to 6.2 recently. We have now found that, the page property 'cq:lastReplicated' is missing from the page properties in Publish server.
From some of the posts I understood that its a design change in AEM 6.2 so we need to disable the component: com.day.cq.replication.impl.ReplicationPropertiesFilterFactory' in Author in order to carry over this property to Publisher.
However I couldn't found this property in AEM author system console. Can anyone let me know is the component is really missing or was i looking for incorrect component?
Appreciate your support!
Thanks,
Sak
Solved! Go to Solution.
Views
Replies
Total Likes
Hi
cq:lastReplicationAction, cq:lastreplicated and cq:lastReplicatedBy properties are not carried over to publish by design. In order to carry over these properties disable the below component in author instance com.day.cq.replication.impl.ReplicationPropertiesFilterFactory
http://localhost:4502/system/console/components
However, this component gets enabled whenever the server restarts. To make it not getting enabled on Server restart add component is below config From OSGi config manager
similar thread Permanently disable ReplicationPropertiesFilterFactory
Thank
Arun
Views
Replies
Total Likes
Hi
cq:lastReplicationAction, cq:lastreplicated and cq:lastReplicatedBy properties are not carried over to publish by design. In order to carry over these properties disable the below component in author instance com.day.cq.replication.impl.ReplicationPropertiesFilterFactory
http://localhost:4502/system/console/components
However, this component gets enabled whenever the server restarts. To make it not getting enabled on Server restart add component is below config From OSGi config manager
similar thread Permanently disable ReplicationPropertiesFilterFactory
Thank
Arun
Views
Replies
Total Likes
Thanks for the quick response Arun.
May i know why Adobe is controlling carry over of 'cq:lastModified' property by default on replication?
Appreciate if you could provide an official documentation on this.
Thanks,
Kishore
Views
Replies
Total Likes
Hi,
On publisher these properties are redundant.
cq:lastmodified on publisher captured same info like q:lastreplicatied
cq:lastmodifiedBy on publisher captured same info like q:lastreplicatiedBy
having cq:lastReplicationAction on publisher make no sense.
Let me find documentation and let you know.
Thanks
Arun
Views
Replies
Total Likes
Can anyone clarify me the difference between lastModified vs lastReplicated. I see both have different timestamps on publish.
Views
Replies
Total Likes
Hi,
There is no rules like cq:lastReplicated and cq:lastModified would have the same timestamp.
cq:lastReplicated - The date the page was last replicated.
cq:lastModified - Date the page (or its paragraphs) was last modified.
There may be latency between last replication timestamp and the time same update on publisher(s).
It is not necessary that cq:lastModified should be same as cq::lastreplication,
cq:lastModified on publisher could be nearer to cq:lastmodified on author
Thanks
Arun
Views
Replies
Total Likes
I understand the 'cq:lastModified' is being updated on each push. However i am not sure whether we can consider 'cq:lastModified' for search engine (google sitemap) crawling. Anyone has thoughts on this?
Views
Replies
Total Likes
Anyone has thoughts on this? Can we consider 'cq:lastModified' for search crawling?
Views
Replies
Total Likes