Last modified: 2011-02-08 21:56:00 UTC
While deleting/restoring Commons's sandbox for some test I also noticed that although the "protect" action is visible in the history-tab after the restore, it doesn't affect anything. That protection-flag doesn't get restored for some reason (wonder what the reason is) is one thing, but when it does get showed in the history and no log of unprotection is seen, that is another thing. The [[commons:Commons:Sandbox]] was indefinite [move=sysop] protected. Then deleted, then totally restored and last "edit" in the history-tab is indeed that protection-action. Yet the page it fully unprotected. -- Krinkle
Protect "action" in history is just a dummy revision inserted to indicate that the page was protected at that point. It has no other functionality and restoring it is not supposed to reinstate protection. No bug here.
I wasn't referring referting to the dummy revision itself. If I protect a page, then unprotect and revert to the dummy revision of the do-protect action I get that it won't make a different in the protection settings. However, if I delete a protected page which has the page properties of it being protected, and restore the page again after deletion I would asume the page properties are not lost but restored aswell.
Another Condition, about protection on create: 1. Protect nonexistant page "AAAA" for new an unregistered users. 2. Now unregistered users aren't able to create page "AAAA" - OK 3. An autoconfirmed user or sysop creates the page "AAAA". 4. A sysop deletes page "AAAA". 5. Now unregistered users are able to create page "AAAA" - BUG! Example: http://es.pokemon.wikia.com/index.php?title=Especial%3ARegistro&page=EP670&uselang=en (protected on November 11, until 25, created by an autoconfirmed user, deleted, and then unregistered users were able to recreate it)
Oww, now I found an older duplicate of this bug. Closing this one. *** This bug has been marked as a duplicate of bug 12343 ***
