When installing a bundle via CRX Package Manager, is it possible to preserve original modification metadata? | Community
Skip to main content
LinearGradient
LinearGradient
Level 6
October 16, 2015
Solved

When installing a bundle via CRX Package Manager, is it possible to preserve original modification metadata?

  • October 16, 2015
  • 3 replies
  • 929 views

Hi,

When installing a bundle via CRX Package Manager, is it possible to preserve original modification metadata:

  • jcr:created
  • jcr:createdBy

If we don't preserve the original values for these attributes, jcr:created will be a point in time after jcr:lastModified which is undesirable for us.

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 Sham_HC

LinearGradient wrote...

In Backup and Restore, Package Manager is specified as a possible means of backing up and restoring content.

We have been using this approach in the past few months as advised by Adobe consultants, however we have noticed that this approach is changing the given metadata properties (i.e. jcr:created, jcr:createdBy) and this is not what we had expected.

This is especially problematic because jcr:created is set to a date after jcr:lastModified which doesn't make sense.

So we are looking for a way to preserve the original values of these properties when we restore a package based backup.

AFAIK no such option to preserve value out of the box. You might have to create a version in package on each back up and restore later which ever version you want.

http://aemfaq.blogspot.com/2013/07/package-manager-view-with.html

3 replies

Sham_HC
Sham_HC
Level 10
October 16, 2015

What is your exact use case?

LinearGradient
LinearGradientAuthor
Level 6
October 16, 2015

In Backup and Restore, Package Manager is specified as a possible means of backing up and restoring content.

We have been using this approach in the past few months as advised by Adobe consultants, however we have noticed that this approach is changing the given metadata properties (i.e. jcr:created, jcr:createdBy) and this is not what we had expected.

This is especially problematic because jcr:created is set to a date after jcr:lastModified which doesn't make sense.

So we are looking for a way to preserve the original values of these properties when we restore a package based backup.

Sham_HC
Sham_HCAccepted solution
Level 10
October 16, 2015

LinearGradient wrote...

In Backup and Restore, Package Manager is specified as a possible means of backing up and restoring content.

We have been using this approach in the past few months as advised by Adobe consultants, however we have noticed that this approach is changing the given metadata properties (i.e. jcr:created, jcr:createdBy) and this is not what we had expected.

This is especially problematic because jcr:created is set to a date after jcr:lastModified which doesn't make sense.

So we are looking for a way to preserve the original values of these properties when we restore a package based backup.

AFAIK no such option to preserve value out of the box. You might have to create a version in package on each back up and restore later which ever version you want.

http://aemfaq.blogspot.com/2013/07/package-manager-view-with.html

Terms & ConditionsAccessibility statement

Loading footer...