Enonic version: 6.15.6
I don’t know if this is a bug, but if it isn’t it would be nice to get an explanation for why this is implemented as it is.
Let us say that I have a content with path “my-content”, and then I decide to change the path to “new-path-for-my-content”. Then later on, I would like to restore the version of the content that contains the original path “my-content”. When restoring to that version everything else that was originally in the this version is restored, but not the path. As I restore the content initially I would expect the path to go back to “my-content”, but what’s happening today is the path continue to be “new-path-for-my-content”.