Added permission (Lockdown) check on db query

[aploe]

I made DPL work with the Lockdown extension. Now DPL only shows Articles from Namespaces that the current user has permission to "read". As I see it, the changes shouldn't touch any other functions or conflict with any other extension.

Just added the user-object (made $wgUser global - I din't know how to get the object with another call) and the Lockdown-array ($wgNamespacePermissionLockdown - also global). Then I compare the "read" part of the Lockdown-array (should hold all groups with "read" permission) against the current user groups and add all namespaces to the $addNotWhere array that shouldn't be seen.

It's not that pretty but works perfectly fine on our wikis.

[Alexia]

Sorry, I had no idea this was actually editing the code in the repository of your fork. O_o That is unexpected behavior from Github I did not expect.

[aploe]

Ah, that's perfectly fine with me. Doesn't change the behaviour at all and does definitly look a bit prettier ;)
And the code changes should be pushed to my fork,. This is how my fork can stay up to date with your master.

[aploe]

I think you still have to merge the pull request ^^