cq:lastReplicated not found in AEM 6.2 publisher page | Community
Skip to main content
S
sakd8248873
Level 2
June 19, 2018
Solved

cq:lastReplicated not found in AEM 6.2 publisher page

  • June 19, 2018
  • 7 replies
  • 3705 views

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

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 arunpatidar

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

7 replies

arunpatidar
Community Advisor
arunpatidarCommunity AdvisorAccepted solution
Community Advisor
June 19, 2018

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

Arun Patidar
S
sakd8248873Author
Level 2
June 19, 2018

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

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
June 20, 2018

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

Arun Patidar
S
sakd8248873Author
Level 2
June 20, 2018

Can anyone clarify me the difference between lastModified vs lastReplicated. I see both have different timestamps on publish.

arunpatidar
Community Advisor
arunpatidarCommunity Advisor
Community Advisor
June 20, 2018

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

Arun Patidar
S
sakd8248873Author
Level 2
June 20, 2018

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?

S
sakd8248873Author
Level 2
June 21, 2018

Anyone has thoughts on this? Can we consider 'cq:lastModified' for search crawling?

Terms & ConditionsAccessibility statement

Loading footer...