Is there a way we can stop updating jcr:created date property in AEM published instance?

Avatar

Avatar

shahrukha567143

Avatar

shahrukha567143

shahrukha567143

05-02-2019

Currently jcr:created date property in working fine in author mode. But when we published a page multiple time the jcr:created date property is updated in published mode. which is basically a wrong. When we published any assest first time it should consider this is created date and do not to update this date on publish instance multiple times. And should only update jcr:lastModified date in published instance multiple times.

Replies

Avatar

Avatar

antoniom5495929

Avatar

antoniom5495929

antoniom5495929

05-02-2019

Hi,

which versione of AEM are you using?

Thanks,

Antonio

Avatar

Avatar

shahrukha567143

Avatar

shahrukha567143

shahrukha567143

05-02-2019

AEM 6.4

Avatar

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K

Avatar

smacdonald2008

Total Posts

12.7K

Likes

1.4K

Correct Reply

2.3K
smacdonald2008

05-02-2019

Avatar

Avatar

Gaurav-Behl

MVP

Avatar

Gaurav-Behl

MVP

Gaurav-Behl
MVP

05-02-2019

Probably versioning is turned on for that node/page/asset. Check that as well.

Avatar

Avatar

shahrukha567143

Avatar

shahrukha567143

shahrukha567143

05-02-2019

But this is not a valuable solution as you suggested to turned off versioning from node/page/asset. Which will lead an issue when we required any old pages to re-use. 

Avatar

Avatar

Gaurav-Behl

MVP

Avatar

Gaurav-Behl

MVP

Gaurav-Behl
MVP

06-02-2019

The way I read your problem statement is that the mentioned behavior exists on publish server. I'm missing the point that why would you want to create the versions on publish server. I'm not able to think of any use case.

To me versioning belongs to author and not publish server.

I would recommend that you first check the existing configurations and validate that versioning is the actual root cause.

Avatar

Avatar

Mike_Thaxton

Avatar

Mike_Thaxton

Mike_Thaxton

26-07-2019

We have a similar need for jcr:created, for analytics purposes.  It doesn't seem to matter if we have versioning on or off, the jcr:created date continues to represent the date it was last replicated.  Is there any way to get the actual, unchanging, date that the node was created on the author (or pub) instance in the first place?  Do we need to create a custom prop on author and persist it?

Avatar

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

953

Correct Reply

1.0K

Avatar

Jörg_Hoh

Employee

Total Posts

3.0K

Likes

953

Correct Reply

1.0K
Jörg_Hoh
Employee

28-07-2019

You should use a dedicated property for that.