View Issue Details

IDProjectCategoryView StatusLast Update
0001315Anope Development (1.9.x series)Chanservpublic2011-08-18 21:52
ReporterRobby Assigned ToAdam  
PrioritynormalSeverityminorReproducibilityalways
Status resolvedResolutionfixed 
PlatformLinux, i686OSFedora 
Summary0001315: [anope-1.9-960c339] '/cs hop|aop|sop #ch add nick' shows wrong levels in '/cs access #ch list'
DescriptionThe ChanServ access list shows wrong levels:
When adding someone as an HOP (lvl 4) the nick has level 5 in the access listing.
When adding someone as an AOP (lvl 5) or SOP (lvl 10) the nick has level 10000 in the access listing.
Steps To Reproduce/CS HOP|AOP|SOP #chan ADD nick
/CS ACCESS #chan LIST
and you will see that the nick has incorrect levels.

/CS HOP|AOP|SOP #chan LIST
does however show correctly to which list the nick is added.
Additional InformationThe channel modes set on the nick are however correct and unaffected, either +h for HOP, +o for AOP or +ao for SOP. The 2 remaining xOP ADD commands work correctly.
TagsNo tags attached.

Activities

Adam

2011-08-18 21:52

administrator   ~0005926

This was because of the CA_ASSIGN permission being allowed in sop, I've moved it to qop.

Robby

2011-08-17 17:03

manager   ~0005924

I can reproduce the SOP-issue with a fresh database too. All other xOP work as expected.

Robby

2011-08-17 16:21

manager   ~0005923

Last edited: 2011-08-17 16:32

View 4 revisions

I didn't change any of the level defaults in the config, perhaps I *did* change the levels through ChanServ at some point in time (years). This database has not been created with this version, it originally comes from 1.8.x and a few weeks back upgraded to 1.9. Looks like something goes wrong with upgraded databases (do note that I didn't test this with a new/fresh database (yet)).

I did however register a new test channel now and there this problem still occurs, but now differently however. Now HOP and AOP correctly adds the user with the appropriate level, but SOP still adds the user as level 10000 instead of level 10.

Here is the level listing of both the channel which existed already and the new channel, seems there's some slight differences in the levels here and there.

This is the level list for the problematic channel:
<Robby> LEVELS #Opers LIST
-ChanServ- Access level settings for channel #Opers:
-ChanServ- ACC-CHANGE 10
-ChanServ- ACC-LIST 1
-ChanServ- AKICK 10
-ChanServ- ASSIGN 10000
-ChanServ- AUTOHALFOP 4
-ChanServ- AUTOOP 5
-ChanServ- AUTOOWNER 10000
-ChanServ- AUTOPROTECT 10
-ChanServ- AUTOVOICE 3
-ChanServ- BADWORDS 10
-ChanServ- BAN 5
-ChanServ- FANTASIA 3
-ChanServ- FOUNDER (founder only)
-ChanServ- GETKEY 5
-ChanServ- GREET 5
-ChanServ- HALFOP 5
-ChanServ- HALFOPME 4
-ChanServ- INFO 10000
-ChanServ- INVITE 5
-ChanServ- KICK 5
-ChanServ- MEMO 10
-ChanServ- MODE 5
-ChanServ- NOKICK 1
-ChanServ- OPDEOP 5
-ChanServ- OPDEOPME 5
-ChanServ- OWNER (founder only)
-ChanServ- OWNERME 10000
-ChanServ- PROTECT 10000
-ChanServ- PROTECTME 10
-ChanServ- SAY 5
-ChanServ- SIGNKICK 10000
-ChanServ- SET 10000
-ChanServ- TOPIC 10000
-ChanServ- UNBAN 5
-ChanServ- VOICE 5
-ChanServ- VOICEME 3

This is the level list for the newly created test channel:
<Robby> LEVELS #Test LIST
-ChanServ- Access level settings for channel #Test:
-ChanServ- ACC-CHANGE 10
-ChanServ- ACC-LIST 1
-ChanServ- AKICK 10
-ChanServ- ASSIGN (founder only)
-ChanServ- AUTOHALFOP 4
-ChanServ- AUTOOP 5
-ChanServ- AUTOOWNER 9999
-ChanServ- AUTOPROTECT 10
-ChanServ- AUTOVOICE 3
-ChanServ- BADWORDS 10
-ChanServ- BAN 4
-ChanServ- FANTASIA 3
-ChanServ- FOUNDER (founder only)
-ChanServ- GETKEY 5
-ChanServ- GREET 5
-ChanServ- HALFOP 5
-ChanServ- HALFOPME 4
-ChanServ- INFO 9999
-ChanServ- INVITE 5
-ChanServ- KICK 4
-ChanServ- MEMO 10
-ChanServ- MODE 5
-ChanServ- NOKICK 1
-ChanServ- OPDEOP 5
-ChanServ- OPDEOPME 5
-ChanServ- OWNER (founder only)
-ChanServ- OWNERME 9999
-ChanServ- PROTECT 9999
-ChanServ- PROTECTME 10
-ChanServ- SAY 5
-ChanServ- SIGNKICK 9999
-ChanServ- SET 9999
-ChanServ- TOPIC 5
-ChanServ- UNBAN 4
-ChanServ- VOICE 4
-ChanServ- VOICEME 3

Adam

2011-08-16 20:33

administrator   ~0005922

I am unable to reproduce this. It is possible you changed the levels of the channel (or the default levels in the config) to give more/less access to different levels thus making XOP to levels conversion change?

Issue History

Date Modified Username Field Change
2011-08-16 01:14 Robby New Issue
2011-08-16 20:33 Adam Note Added: 0005922
2011-08-16 20:33 Adam Assigned To => Adam
2011-08-16 20:33 Adam Status new => feedback
2011-08-17 16:21 Robby Note Added: 0005923
2011-08-17 16:21 Robby Status feedback => assigned
2011-08-17 16:25 Robby Note Edited: 0005923 View Revisions
2011-08-17 16:26 Robby Note Edited: 0005923 View Revisions
2011-08-17 16:32 Robby Note Edited: 0005923 View Revisions
2011-08-17 17:03 Robby Note Added: 0005924
2011-08-18 21:52 Adam Note Added: 0005926
2011-08-18 21:52 Adam Status assigned => resolved
2011-08-18 21:52 Adam Resolution open => fixed