Change Details

[[ https://www.mediawiki.org/wiki/Manual:Hooks/PageDeleteComplete | PageDeleteComplete hook ]] gives us comprehensive info about the page delete, after it happens. The older [[ https://www.mediawiki.org/wiki/Manual:Hooks/ArticleUndelete | ArticleUndelete hook ]] does not! We do not get timestamp of Undelete, nor do we get the performer. Instead, we have to guess that the current timestamp is close enough to the time of the undelete, and we have to guess that the current ` RequestContext::getMain()->getUser()` is the performer, relying on some global state. Can we make a PageUndeleteComplete hook?

[[ https://www.mediawiki.org/wiki/Manual:Hooks/PageDeleteComplete | PageDeleteComplete hook ]] gives us comprehensive info about the page delete, after it happens. The older [[ https://www.mediawiki.org/wiki/Manual:Hooks/ArticleUndelete | ArticleUndelete hook ]] does not! We do not get timestamp of Undelete, nor do we get the performer. Instead, we have to guess that the current timestamp is close enough to the time of the undelete, and we have to guess that the current `RequestContext::getMain()->getUser()` is the performer, relying on some global state. Can we make a PageUndeleteComplete hook?

[[ https://www.mediawiki.org/wiki/Manual:Hooks/PageDeleteComplete | PageDeleteComplete hook ]] gives us comprehensive info about the page delete, after it happens. The older [[ https://www.mediawiki.org/wiki/Manual:Hooks/ArticleUndelete | ArticleUndelete hook ]] does not! We do not get timestamp of Undelete, nor do we get the performer. Instead, we have to guess that the current timestamp is close enough to the time of the undelete, and we have to guess that the current ` RequestContext::getMain()->getUser()` is the performer, relying on some global state. Can we make a PageUndeleteComplete hook?