On 2016-12-20 06:22, Daniel Barrett wrote:
>>> My goal is to remove some special pages for anonymous users but permit
>>> logged-in users to see them.
>>> Is there a better way to check for a logged-in user at this hook point?
>>> Or a better way to remove special pages for anonymous users?
On Tue, Dec 20, 2016 at 2:00 AM, Bartosz Dziewoński
wrote:
> On 2016-12-20 06:22, Daniel Barrett wrote:
>
>> The real issue is that a custom callback for the hook
>> "SpecialPages_initList" is invoking RequestContext::getMain()->get
>> User()->isLoggedIn().
>>
>> Apparently
On 2016-12-20 06:22, Daniel Barrett wrote:
The real issue is that a custom callback for the hook "SpecialPages_initList" is
invoking RequestContext::getMain()->getUser()->isLoggedIn().
Apparently that doesn't work.
I'll take a guess that SpecialPages_initList runs too early for this check to
OK, I have traced the issue, and I'm embarrassed to say, it's in a custom
extension.
(I removed the extension yesterday and the error kept happening, so I figured
the extension
was harmless... but I'll bet I was fooled by browser caching.)
Apologies if my incorrect information wasted anyone's