Last modified: 2007-10-13 04:04:13 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T13609, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 11609 - isAllowed hook
isAllowed hook
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
User blocking (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2007-10-09 01:11 UTC by Aran
Modified: 2007-10-13 04:04 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Aran 2007-10-09 01:11:06 UTC 
I've been looking at the code surrounding security, and I'm wondering why the userCan hook isn't called from isAllowed since most of the calls made to determine whether an action can be performed call userCan, yet all of them call isAllowed. Even if userCan is best where it is, wouldn't it be a good idea to have an isAllowed hook?
Comment 1 Aran 2007-10-09 01:12:17 UTC 
(sorry I meant most *dont* call userCan)
Comment 2 Aran 2007-10-13 04:04:13 UTC 
Silly me, there's no need for such a hook since the result it returns is determined by the global array which can be adjusted. Sorry :-/
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links