Last modified: 2013-10-23 18:15:24 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 T39466, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 37466 - userCan or getUserPermissionsErrors hooks seem not to work in MW 1.18.3
userCan or getUserPermissionsErrors hooks seem not to work in MW 1.18.3
Status: RESOLVED WORKSFORME
Product: MediaWiki
Classification: Unclassified
User blocking (Other open bugs)
1.18.x
All All
: Unprioritized major (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-11 15:28 UTC by Toni Hermoso Pulido
Modified: 2013-10-23 18:15 UTC (History)
1 user (show)

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


Attachments

Description Toni Hermoso Pulido 2012-06-11 15:28:21 UTC
Sorry if not the suitable component.
I've checked whether is a problem with extension http://www.mediawiki.org/wiki/Extension:Lockdown but I would dare to say that is a MW problem, and userCan or getUserPermissionsErrors hooks are not working.

They do work for 1.19, though.
Comment 1 Andre Klapper 2012-11-14 13:23:50 UTC
Hi Toni! Sorry that nobody has taken a look at this report yet and given feedback.

Where to reproduce this (web address)? Is this a private wiki, or some public page? Is this still a problem or did you find a workaround in the meantime (e.g. upgrading to 1.19, as you mention that there is no problem in that version)?
Maybe http://www.mediawiki.org/wiki/Manual:How_to_debug could also provide some hints how to get more info what goes wrong?
Comment 2 Toni Hermoso Pulido 2012-11-14 13:45:43 UTC
Hi Andre,

I must say I already migrated all my 1.18 wikis to 1.19.x. So I cannot tell now :(
Comment 3 Andre Klapper 2012-11-14 13:50:18 UTC
No problem at all - happy that it works for you with a more recent version, and 1.18 will see its end of life very soon anyway. Thanks for the update!

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links