Split off from bug 31469.
Basically, wfMsgForContent, called during the parsing process, was expanding {{NAMESPACE}} incorrectly (As in for the wrong page) during linksupdate jobs from the job queue.
That probably shouldn't happen.
I fixed the immediate issue with the particular wfMsgForContent call in r107623, but the underlying issue was not addressed.
Version: 1.20.x
Severity: normal