Last modified: 2011-03-13 18:06:14 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 840 - introducing user_rights for Enotif: isAllowedToReceiveEnotifsFor.....
introducing user_rights for Enotif: isAllowedToReceiveEnotifsFor.....
Status: CLOSED WONTFIX
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.5.x
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 767
Blocks: 866 2422
  Show dependency treegraph
 
Reported: 2004-11-08 01:15 UTC by T. Gries
Modified: 2011-03-13 18:06 UTC (History)
0 users

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


Attachments

Description T. Gries 2004-11-08 01:15:39 UTC
I propose to introduce two new user_rights:

(1) user is allowed to receive enotifs for user and user_talk page changes
(2) user is allowed to receive enotifs for all page changes

The Enotif program will then simply check the rights before actually sending
mail(s) to a certain watching user if and only if all other conditions are met:
Admin allows and user opted-in. The Enotif program is ready to use such rights;
please can you set these up, Brion ? 

Need some smart names, isAllowedToReceiveEnotifsForUserPageChanges is far too
long, isn't it ? Please let me know, how you think about this proposal.
Comment 1 T. Gries 2004-11-10 17:04:44 UTC
Can someone of the HEAD developers comment this, please ? 

I proposed these new user rights, so that a forthcoming Enotif module can check,
if a user might receive email notification at the stored address.

As usual, I am open for any valuable comment or hint.

Tom
Comment 2 Antoine "hashar" Musso (WMF) 2004-11-10 19:53:18 UTC
Feel free to add new rights:

Add a string defining the new rights to $wgAvailableRights (in Define.php).

Then call the method User:isAllowed($right);

Where $right is a string in $wgAvailableRights.

Example:

if( ! $wgUser->isAllowed('block') ) {
// print error message: not enough rights to access this page 
} {
// do something
}
Comment 3 T. Gries 2004-11-25 01:17:47 UTC
Thank you Ashar for your remark.

Here is what I implemented in Enotif 2.00 for CVS (coming on 30.11.2004):

It might be necessary to lower email traffic for Enotif
http://bugzilla.wikipedia.org/show_bug.cgi?id=454 to a certain needed mininum.
For this reason it is advantageous to introduce user rights to allow Sysops to
select a subset (e.g. power users) of all users which only are allowed to
receive Enotifs for a) user_talk page changes and/or b) all watched page changes.

The new rights  I am introducing are:

1. rcv_enotif_usertalkpage  (if set, this user X sees the user option in
preferences, where s/he can opt-in to have enotifs for changes on the user_talk
page X)

2. rcv_enotif_allpages (if this is set, this user X sees also the option in
preference, where s/he can opt-in to have enotifs for changes on all the
watch-listed pages)

3. emailaddr_authenticated (this means, that the emailaddr is authenticated anc
can be used by UserMailer to send generously enoitfs (dependent on rights under
1. and 2., and the user preferences for this) .

regarding emailaddr_authentication, i am now impleementing the proposal
http://bugzilla.wikipedia.org/show_bug.cgi?id=866 (Email authentication by a
dummy "forgot my password" cycle)

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


Navigation
Links