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

Avatar

Avatar
Validate 1
Level 1
shahrukha567143
Level 1

Likes

0 likes

Total Posts

14 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Give Back 3
Give Back
Ignite 1
View profile

Avatar
Validate 1
Level 1
shahrukha567143
Level 1

Likes

0 likes

Total Posts

14 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Give Back 3
Give Back
Ignite 1
View profile
shahrukha567143
Level 1

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
Establish
Level 6
antoniom5495929
Level 6

Likes

91 likes

Total Posts

212 posts

Correct reply

39 solutions
Top badges earned
Establish
Give Back 50
Give Back 5
Give Back 3
Give Back 25
View profile

Avatar
Establish
Level 6
antoniom5495929
Level 6

Likes

91 likes

Total Posts

212 posts

Correct reply

39 solutions
Top badges earned
Establish
Give Back 50
Give Back 5
Give Back 3
Give Back 25
View profile
antoniom5495929
Level 6

05-02-2019

Hi,

which versione of AEM are you using?

Thanks,

Antonio

Avatar

Avatar
Validate 1
Level 1
shahrukha567143
Level 1

Likes

0 likes

Total Posts

14 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Give Back 3
Give Back
Ignite 1
View profile

Avatar
Validate 1
Level 1
shahrukha567143
Level 1

Likes

0 likes

Total Posts

14 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Give Back 3
Give Back
Ignite 1
View profile
shahrukha567143
Level 1

05-02-2019

AEM 6.4

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,409 likes

Total Posts

12,671 posts

Correct reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,409 likes

Total Posts

12,671 posts

Correct reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

05-02-2019

Avatar

Avatar
Boost 250
MVP
Gaurav-Behl
MVP

Likes

250 likes

Total Posts

1,147 posts

Correct reply

283 solutions
Top badges earned
Boost 250
Establish
Give back 300
Give Back 50
Give Back 5
View profile

Avatar
Boost 250
MVP
Gaurav-Behl
MVP

Likes

250 likes

Total Posts

1,147 posts

Correct reply

283 solutions
Top badges earned
Boost 250
Establish
Give back 300
Give Back 50
Give Back 5
View profile
Gaurav-Behl
MVP

05-02-2019

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

Avatar

Avatar
Validate 1
Level 1
shahrukha567143
Level 1

Likes

0 likes

Total Posts

14 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Give Back 3
Give Back
Ignite 1
View profile

Avatar
Validate 1
Level 1
shahrukha567143
Level 1

Likes

0 likes

Total Posts

14 posts

Correct reply

0 solutions
Top badges earned
Validate 1
Give Back 3
Give Back
Ignite 1
View profile
shahrukha567143
Level 1

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
Boost 250
MVP
Gaurav-Behl
MVP

Likes

250 likes

Total Posts

1,147 posts

Correct reply

283 solutions
Top badges earned
Boost 250
Establish
Give back 300
Give Back 50
Give Back 5
View profile

Avatar
Boost 250
MVP
Gaurav-Behl
MVP

Likes

250 likes

Total Posts

1,147 posts

Correct reply

283 solutions
Top badges earned
Boost 250
Establish
Give back 300
Give Back 50
Give Back 5
View profile
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
Level 1
Mike_Thaxton
Level 1

Likes

0 likes

Total Posts

1 post

Correct reply

0 solutions
View profile

Avatar
Level 1
Mike_Thaxton
Level 1

Likes

0 likes

Total Posts

1 post

Correct reply

0 solutions
View profile
Mike_Thaxton
Level 1

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
Coach
Employee
Jörg_Hoh
Employee

Likes

1,134 likes

Total Posts

3,161 posts

Correct reply

1,079 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile

Avatar
Coach
Employee
Jörg_Hoh
Employee

Likes

1,134 likes

Total Posts

3,161 posts

Correct reply

1,079 solutions
Top badges earned
Coach
Give back 600
Ignite 5
Ignite 3
Ignite 1
View profile
Jörg_Hoh
Employee

28-07-2019

You should use a dedicated property for that.