Hi,
I have a (private) module that basically does this:
$entity = EntityTypeManager::getStorage('node')->load(...);
/* Set some fields */
$entity->setNewRevision(true);
$enttiy->save();
With the expectation that it would update a couple of fields, create a new entity, and then save said entity with a new revision and its own revision_timestamp reflecting when that revision is made.
The problem is that this has a side effect: it's updating the revision_timestamp of all other revisions of this entity to that of the latest one, effectively clobbering all of my revisions to reflect the latest revision time, losing any record of when all earlier revisions were actually created.
Am I missing a step somewhere and this is intended behavior, or is this an oversight?
Closed: outdated
9.5
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Can you reproduce this on a vanilla install of Drupal core?
If so can you add more steps to reproduce.
This isn't the default behaviour so I suspect something else might be in the mix here.
Since there hasn't been a follow up going to close for now.