Issue: Automatic edit from nowhere

Did you or another user perform any tasks like:

• Rebuild all URLs in the wiki
• Add this page to a book or remove it from one
• Modify one of the page's behaviors
• Perform any moderator act (approving, moving, deleting, etc) involving this page
• Anything else you can think of

There are some situations where a previous version will be erroneously duplicated, but it will always require some sort of action involving the page where the duplication occurs. When duplication occurs, it is important for us to know what kind of action triggered it and more information about the page and its field values. Maybe certain characters in the title are mistakenly detected as changed, or maybe some other field that is expected to change is not properly being excluded from detection.

None of the above were performed.
I am not sure what the cause could be. The edit is not in the xf newsfeed. there is also no other activity listed in XF or VW newsfeeds at that time. The only thing that happened somewhat close to the same time is that I upgraded moderator essentials an hour earlier. And possibly some users accessed the site and thereby triggered defferred.php but that is guesswork.

It's possible that it used to be in a book and someone removed it as a chapter from the book. Removal of a chapter would not appear in any feed, so that could be why we don't know what action triggered it. As of 4.0.15, similar actions were incorrectly being considered for new revisions. This is already fixed in the next release, on the grounds that it was a waste of time to process if there was no edit.

However, even if there was an action that should be considered for a new revision, if there was no change, it still shouldn't create a new revision. For this reason, I leave the report open.

I was able to duplicate the latest revision by adding the affected page to a random book. This will not be possible in the next release, but I can now look into why the page was considered changed.

Okay, I have determined that a bug that started in RC 5 results in the second-to-last revision being treated as the last revision in virtually every case. This will almost always result in a new revision -- unless we are making changes back to the second-to-last revision; in which case, nothing would happen.

This occurs because the internal field for specifying what revision we are editing has the same field name as the page's current revision's parent revision ID.

This is now fixed in the next release.