View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003098 | unreal | ircd | public | 2006-10-26 00:46 | 2007-04-18 04:50 |
Reporter | Robby22 | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | duplicate | ||
Platform | i686 | OS | Fedora Core | OS Version | 5 |
Product Version | 3.2.5 | ||||
Summary | 0003098: Net/Server-Admin (and probably regular oper also) with can_override and being halfopped can't -qao someone, but can +qao | ||||
Description | It seems that when an operator, in this case a NetAdmin, who is halfopped in a channel and has the can_override flag, cannot set another user -qao but CAN set +qao, -v or +v does work normally by the way. Also, when specifying any other modes along with the +m, like -ao, for example, doing '/MODE #channel +m-ao UserX UserX' generates an override notice for +m and displays this in the status window: a UserX is a channel admin o UserX is a channel admin While doing just '/MODE #channel +m' does not generate any notice, as halfops can set that mode anyway. | ||||
Steps To Reproduce | To summarize again: when the NetAdmin with can_override who is halfopped in the channel wants to set a user -q/-a/-o, they first have to +o/+ao/+qo OR -h themselves before they can -q/-a/-o someone. Setting someone +q/+a/+o while being halfopped works like it should, as does setting +v or -v, but not combined like for example '/MODE #channel -aov UserX UserX UserX', then -v does not work either. | ||||
Tags | No tags attached. | ||||
3rd party modules | |||||
duplicate of | 0002973 | closed | override bug |
|
Yes, I have seen this aswell. ;p |
|
maybe this should be made a child of the 3.2.7 report? i can also verify that this bug does indeed exist, and I have noticed it for quite some time. |
|
i swore we took care of that bug in this release...or the one before, but maybe im just confused, though I honestly though it was reported && fixed -Edited to fix "fixes" to 'fixed' |
|
If it was taken care of, why is this not closed/resolved then? ;) I doubt it is, I would certainly have seen something about it in the Changelog, I always check it in CVS... and it is still present (I just tested it a minute ago, so... still broken). Edit: Tested on a recent CVS version (.626) from 2007/01/22 btw |
|
Duplicate of 2973 |
Date Modified | Username | Field | Change |
---|---|---|---|
2006-10-26 00:46 | Robby22 | New Issue | |
2006-10-26 01:01 | charmed6229 | Note Added: 0012514 | |
2007-01-27 20:48 | djGrrr | Note Added: 0013130 | |
2007-02-13 18:17 | Bricker | Note Added: 0013213 | |
2007-02-14 18:16 | Robby22 | Note Added: 0013216 | |
2007-02-14 18:20 | Robby22 | Note Edited: 0013216 | |
2007-02-15 17:19 | Bricker | Note Edited: 0013213 | |
2007-04-17 17:52 | WolfSage | Note Added: 0013486 | |
2007-04-18 04:50 |
|
Relationship added | duplicate of 0002973 |
2007-04-18 04:50 |
|
Status | new => closed |
2007-04-18 04:50 |
|
Resolution | open => duplicate |