Logfile "include network" & "networkless" servers - 11/01/16 05:46 AM
With the "include network" option enabled on logging, when a server does not supply any network name, i.e. $network is null (think private and probably not-ideally configured servers), the following bugs happen:
But for added bonus, things get wildly confusing when a channel by the same name is simultaneously used on a "network-named" server:
Suggestion: For logging with network name in filename/folder, fall back to server name if no network is stated.
- No network name is appended to the logfile name, it results in #channelname.log
- If "create folder" is enabled in logging options, no folder is created, logfiles for the "networkless" server end up in main directory
But for added bonus, things get wildly confusing when a channel by the same name is simultaneously used on a "network-named" server:
- Without "use folders", the logfile from the "network-less" channel ends up in the wrong channel (I guess the one that is first re-entered), resulting in a wildly mixed backlog in that channel window.
- When "use folders" is enabled, messages from both channels are mixed up into the respective logfile of the "network-named" server.
Suggestion: For logging with network name in filename/folder, fall back to server name if no network is stated.