Last modified: 2014-03-14 11:14:12 UTC
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.
This bug is not actionable. Nowdays we recommend passing context always when possible, in which case the title should be correct as well. There is no other way to fix it.