This issue is present on Drupal 10 (fixed in Drupal 11.1) The 'last saved' date on a page should not be update (when the 'new revision' option is not checked).
Run Tidy on a page that will be updated. (or create a new one and wait at least 2 minutes before running tidy on it)
The timestamp shown for the 'last saved' has been updated :(
Update the fixerProcessSave to include logic to retain the timestamp.
See the Core issue for further info: Allow ChangedItem to skip updating the entity's "changed" timestamp when synchronizing
There's a D10 patch in the comments of the same issue that _may_ be helpful, but I would recommended moving to Drupal 11.
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
compare changes, plain diff MR !5
Comments
Comment #2
jasongose commentedComment #4
jasongose commentedLooks like the behavior changed in Drupal 11.1 so that the changed timestamp isn't updated if setSyncing(TRUE) is used, Allow ChangedItem to skip updating the entity's "changed" timestamp when synchronizing
Comment #6
jasongose commentedPrior to Drupal 11.1 you could not save an entity without updating the timestamp. I would recommend updating to Drupal 11 prior to running Link Magician if this is problematic for your site.
Comment #7
jasongose commentedComment #9
jasongose commented