This is an old issue I have with Sitefinity and it has to do with enabling/disabling the "This page redirects to another page" feature.
An editor has a page on their website that is no longer in use, but it's important for this page to be redirected to alternative content for SEO purposes.
Enable the option "This page redirects to another page" option for this page.
It seems the revision history is purely for content on the page and doesn't include anything to do with the page properties.
We've had this on so many occasions and it is painful to try and explain this to our customers, but the most recent one is where a customer changed the page to "This page redirects to another page" and didn't realise that this would trash the page.
Here's the major problems:
It would make far more sense if:
The only alternative solution I can think of is to move the page in question to an unpublished grouping page called say "Unused", then change it's URL to make sure it can't be found directly. Then create a dummy page in the same location as where the page originally existed, make sure it's URL matches the old URL then change it to be a redirecting page. In this way you retain the content of the previous page whilst still getting the redirect that you were looking for.
Seems like there should be a better way to handle this.
I noticed that both these are actually duplicate feature requests. Does your feature request system allow for merging of items as well as their 'following' and 'likes/dislikes' data?