Publishing a content changes value in modifiedTime

[alansemenov]

When a content item is published we create a new version and set publish.first. This also causes modifiedTime to be updated with current date/time. We need to avoid modifiedTime being updated. It's common to have content sorted by modifiedTime and publishing should not affect this order.

[GlennRicaud]

We are modifying the content, so the modifiedTime should be updated.
The problem here is the original solution: Setting a value on a content on a publish. It is not only wrong but makes the initial publish 4 times slower.

[GlennRicaud]

I will close this issue.

IMHO, we should fix the way we do the publish and scheduled publish in 7.0.
Use the createdTime of the master version (instead of publish.first) and have scheduled task for the future for scheduled publish (instead of publish.from and publish.to)
I added it to the 7.0 backlog

[sigdestad]

One second.. Yes, we are modifying the node - but we are not modifying the "content/data" which is what this attribute is about. The timestamp value for nodes will change, that is fine - but we definetly do not want to register this as a modification of the content. I guess we should simply not use the content API to add the publish.first value.

NB! publish.first is a completely different value from created. You can create an item today, and then publish it tomorrow.

[sigdestad]

So, logically the modifiedTime value is wrong, and must not be set as part of the publish process.

[sigdestad]

It actually breaks a lot of things when this value is changed as part of the publishing process.

[GlennRicaud]

Yes. I thought about it after and I definitely talked too fast here.
You are right about timestamp/modifiedTime and I also take back the solution proposed for 7.0 which is also wrong.

modifiedTime is not only about the content/data though. It is also modified on modifications on all the other properties: language, owner,… (which makes sense).
But I agree about making an exception for publish.first/publish.from in this specific case.