Age | Commit message (Collapse) | Author |
|
fixed not displaying the channelmodes
|
|
after unserializing persist on
|
|
|
|
|
|
|
|
|
|
|
|
This reverts commit 3b8f1cd59f523205d96c54c517b4d3e06bc061c4.
|
|
|
|
|
|
under us while we are running
|
|
|
|
nicks/channels always end up with the defaults enabled, even if they explicitly have them set off. Fix setting nickserv defaults to none.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Update placeholder text for hostmask
|
|
cs_access: Fixed disabling channel levels. Also, correctly log /cs levels commands.
|
|
|
|
the input is invalid
|
|
commands as an override or a normal command at the time it is executed, so, right before levels actually get modified.
|
|
|
|
|
|
|
|
Robby says so
|
|
already exists. Also force command names lowercase when looking them up.
|
|
|
|
doesn't exist
|
|
|
|
entries on the channel
|
|
identified to use. This changes the behavior of hideprivilegedcommands to only hide commands users don't have the oper privileges to execute.
|
|
|
|
|
|
is loaded before the protocol module
|
|
ns_identify: When logging failures, also show the account name, and that it exists or not.
|
|
|
|
|
|
/cs flags, also spotted by TGS
|
|
CREATE EVENT chanstats_event_cleanup_weekly failed due to calculating im...
|
|
chanlist functionality, add a couple of missing ESCAPED_CHANNEL vars
Add missing ESCAPED_CHANNEL
Changed EMAIL_TYPE to FORCE_EMAIL. Now makes more sense
Make it more obvious when the 'email' field is optional
Add a 'Retry' button to go back to the registration page
Fixed broken chanlist functionality. Before even if the user clicked on the channels nothing happened, now it goes straight to the 'set' page (at least something happens)
Small fix, disable the 'Save' button if user has no SET powers
Add another missing ESCAPED_CHANNEL
Add a more clear definition of what hostmasks are allowed in that field, either user@host or nick\!user@host
Fix wrongly placed var
Changed some aesthetics
|
|
improper start of week.
|
|
exists or not.
|
|
|
|
a copy of ChanAccess
|
|
and not by privilege set, as two entries can have the same privset but different levels, but still represent two different levels of access. This prevented users from adding other users at a lower access level when that level had the same privset as them. Spotted by TSG.
|
|
|