Last modified: 2013-11-03 19:16:49 UTC
The new page log does not include redirects created by page moves, even with 'show redirects' enabled. Including them would probably be unnecessary clutter, but not including them means you can do things like this: * Pick any existing page "Foo" and move it to non-existing title "Bar" * Immediately move "Bar" back to "Foo" * Replace the redirect left at "Bar" with something else ...and you have created a new page "Bar" which has no entry in the new page log. Is there some way to fix this without having to include page move redirects?
This isn't really useful for vandals due to all of the move log entries of a page to a wrong title and back. I don't think this otherwise occurs much... That said...I suppose one could check page_is_new and page_is_redirect on edit and flag pages in RC as "new" if it is not a redirect anymore...
Yeah, I agree it's not very useful for vandals (though you could probably fool RC patrol by moving a user subpage there and back, pretending to be moving an article you started and then reverting yourself... sssh don't tell anyone). I just thought it was worth mentioning as a possible inconsistency in the way things were handled. But then it seems there's lots of those. :)
*** Bug 29286 has been marked as a duplicate of this bug. ***
Quoting myself from Bug #29286: Similar to bug #12363 (which covers userspace moves into mainspace), in that both are loopholes in the coverage of Special:Newpages. Redirects converted into articles do not show up as needing to be patrolled. Yet such pages are in some cases particularly likely to need patrolling, since in some cases a decision has already been made that an article is not warranted. I mention this because comment #1 talks about existing articles being moved out of the way, and the resulting redirect then converted into an article. The case I was considering was existing redirects later being converted by someone else. The same solution will presumably apply to both, but it is a different scenario, and I think an additional motivation for addressing this bug.
