Last modified: 2008-12-12 04:55:20 UTC
It's possible to "unprotect" a page without protection ever having been set. If you use &action=unprotect on a page and confirm the protection, it leaves a log entry.
Generally this wouldn't really matter, however, people sometimes use scripts and they accidentally hit the wrong button / link, causing an awkward log entry.
Fixed in r30020
Apparently this is still possible. http://en.wikipedia.org/w/index.php?title=Special%3ALog&type=protect&user=&page=User%3ARjd0060%2Fprottest&year=&month=-1
Status changed to REOPENED.
Created attachment 5042 [details]
change to Title.php
A change similar to r30020 to check the return of the SQL UPDATE/DELETE of Title Protection should fix this?
Tests 1-4 before patch, tests 5-12 after.
Confirmed this behavior on my testwiki, and, confirmed the patch as working.
Done in r36967
Still having this issue. See http://en.wikipedia.org/w/index.php?title=Special%3ALog&type=protect&user=&page=User+talk%3ARjd0060%2Ftest&year=&month=-1 .
I set an expiry and a protection reason and clicked confirm, which logged the unprotection, even though the page was never protected.
Fixed in r44493