View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0000518||unreal||ircd||public||2002-12-11 00:35||2004-02-03 19:03|
|Platform||Intel i686||OS||Windows||OS Version||XP Pro|
|Summary||0000518: /sajoin problems with channel modes +bilk|
|Description||The sajoin command should check target channel modes to see if the command can succeed before executing it. As it is the ircd doesn't give any feedback to the net admin when the forced user fails to join because of a channel mode.|
|Steps To Reproduce||1) Be a net admin and a channel op.|
2) Set channel to invite only, limited to 1 client, set a key, and ban a user.
3) Use /sajoin command to force a user to join the channel.
|Additional Information||As the net admin you will get a notice like: *** Notice -- ferd used SAJOIN to make ferd2 join #limbo but ferd2 won't join. ferd2 will get a notice like: *** You were forced to join #limbo. This will be followed by an error message like: #limbo can't join channel (address is banned).|
|Tags||No tags attached.|
|3rd party modules|
|This will be difficult if not "impossible" to do, but I'll look into it.|
||*bump*. This is the original bugreport, the same was suggested by TimeFx (THANKS!!!!!!!!!!!) reported ~2 weeks ago.|
I think I'll do this for sajoin but not svsjoin. Reason is, svsjoin is commonly used for "autojoin lists" so that would mean, I'm banned from #chan so all I have to do is add to my NS autojoin list and I can get around that.
||codemastr: my solution was, in my operjoin module, to add a new variable (aClient *) as a parameter to the do_join function, which points to the sender of the sajoin command, or NULL in the case of a normal join, and it wasn't difficult and works well. Just an idea.|
|Fixed in .2070|
||Note Added: 0004837|
|2004-02-01 11:20||AngryWolf||Note Added: 0004838|
||Status||acknowledged => resolved|
||Resolution||open => fixed|
||Assigned To||=> codemastr|
||Note Added: 0004858|