ejabberd - Comments for "Modified ACL and now get read errors with Jabber Clients"

ejabberd.cfg is never

mfoss — Mon, 11 Sep 2006 12:05:48 +0000

ejabberd.cfg is never modified. Some configuration changes you make on the web admin are stored on the database (users, rosters, ACL and Access), and others aren't (listening sockets and modules).

I decided to ask in this

Makc666 — Mon, 11 Sep 2006 12:00:09 +0000

I decided to ask in this topic.

In Web Admin I make ANY changes for my sever configuration.
For example I change some mod_* settings.

Then I stop ejabberd and star it again.
When I go to Web Admin interface I see that none of those changes have been saved.

Also I see that ejabberd.cfg file was not changed during stop-start.

How I can make so that all changes in Web Admin were saved after server restart?

Thanks

That works.

gonoles_1980 — Fri, 08 Sep 2006 22:22:42 +0000

So simple :(, I feel like a dunce.

Thanks a bunch for the help :).

Reload and override

legoscia — Fri, 08 Sep 2006 10:18:59 +0000

At the top of your ejabberd.cfg, there is a line:

%override_acls.

Remove the % sign at the beginning. Then follow the instructions for reloading the configuration.

(The % sign is the Erlang comment sign. Removing it thus makes the directive override_acls active, which is what you need in this case.)