> This happens because a number of users requested support for multi-user > environments in which not all users are TMDA users. > [...]
Right. I know that (and actually, I will probably end up in that situation). But why doesn't it know the correct username? Or rather, why is $username empty? > The plugin forces a logout if the file that you are trying to edit does not > exist. This could indicate that you have not modified the sample > configuration file and the default entry for, say, "Whitelist" (which is > ~/.tmda/lists/whitelist) is not valid on your system. The file definitely is there, and I'm pretty sure I set up permissions correctly, but its still happening. > In hindsight this is probably not a good idea and i'll remove it from the > next version - a simple "file not found" message will suffice - and aid in > setting up the plugin. Couldn't you just make inaccessible files disappear from the selection? That way I could add more files to the configuration and those users who don't use them wouldn't even notice. johannes _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
