https://www.ejabberd.im/node/779 en https://www.ejabberd.im/node/779#comment-1643 <p>Yes, somehow I missed section "A.9 mod_muc_log" in the Installation and Operations Guide.</p> <p>My mistake was putting the settings under {mod_muc} instead of separately in {mod_muc_log}. Once I did that JWChat showed the configuration item when clicking on 'config'.</p> <p>I also found in when using tkabber. You have to click on the 'Subject:' text to find the configuration menu on the chat screen.</p> <p>It's now working great!</p> Fri, 28 Apr 2006 20:03:47 +0000 jperegrino comment 1643 at https://www.ejabberd.im https://www.ejabberd.im/node/779#comment-1628 <p>You forgot to check the ejabberd guide: it contains the definitive documentation.</p> <p>By the way, you don't need to specify all the options if the default values are good enought for you. For example, a typical config can be:</p> <pre>{mod_muc_log, [ {outdir, "/var/www/muclogs"}, {top_link, {"http://www.jabber.ru/", "Jabber.ru"}} ]},</pre><p> Once you correctly enable the module, a new option will appear on the chatroom config form. </p> <p>JWChat should be capable of that. Admin-friendly clients for *nix: <ul> <li>Tkabber: CVS version includes ad-hoc support. Try this binary: <noindex><a href="http://tkabber.jabber.ru/starpack" rel="nofollow" >Tkabber-Starpack</a></noindex> </li><li>Gajim: lacks ad-hoc </li><li>Psi 0.11-beta2: lacks MUC </li><li>Coccinella: lacks ad-hoc </li></ul> </p> Thu, 27 Apr 2006 21:27:17 +0000 mfoss comment 1628 at https://www.ejabberd.im