ejabberd 2.1.3 - Third bugfix release

ejabberd 2.1.3 has been released. It contains many bugfixes and some improvements.

This is a short list of changes:

  • New ejabberd_c2s option: max_fsm_queue
  • ejabberdctl: Support concurrent connections with bound connection names
  • Cross-domain HTTP-Bind support (EJAB-1168)
  • Hibernate http-bind process after handling a request
  • LDAP: document ldap_dn_filter, and fetch only needed attributes in search (EJAB-1204)
  • Fix MSSQL support, which was broken (EJAB-1201)
  • Improved SQL reconnect behaviour
  • PEP: Add extended stanza addressing 'replyto' (EJAB-1198)
  • PubSub: Add pubsub#purge_offline (EJAB-1186) and Fix pubsub#title option (EJAB-1190)
  • Optimizations in mod_caps
  • mod_register: Add new acl access_from, default is to deny
  • mod_sic: new module for the experimental XEP-0279 Server IP Check (EJAB-1205)
  • Proxy65: new option hostname (EJAB-838)
  • Shared Roster Groups: get contacts nickname from vcard (EJAB-114)

Check the 2.1.3 Release Notes for the full list of fixes and improvements.

The list of solved tickets since ejabberd 2.1.2 is available on ProcessOne bug tracker: http://redir.process-one.net/ejabberd-2.1.3

If you upgrade from ejabberd 2.0.5 or older, read carefully the release notes of ejabberd 2.1.0 too, because there were several changes in the installation path and the configuration options.

The source package and binary installers for Linux 32 bits, 64 bits, Mac OS X Intel, and Windows are available in the ejabberd ProcessOne download page.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

database empty

Just one problem: I have upgraded from 2.1.1 to 2.1.3, copied entire dir "database" from 2.1.1, but when I log in through web admin, I see empty database - no users.

What have I done wrong?

how to transfer mnesia db between versions?

BTW how about the accounts issue?
What is needed to successfully transfer user accounts between ejabberd versions? I thought I would only need to copy the "database" dir since this is just a minor version upgrade (from 2.1.1 to 2.1.3) and I supposed the db structure hadn't changed. Or had it?

Forum question

Pontiac wrote:

BTW how about the accounts issue?

That isn't a question about this ejabberd 2.1.3 release announcement, so it should go to a forum thread.

which Erlang compilator for 2.1.3?

I am going to download R13B04 from Feb 24, 2010, is it OK for 2.1.3?

Thank you


Pontiac wrote:

I am going to download R13B04 from Feb 24, 2010, is it OK for 2.1.3?

ejabberd binary installers already include the required parts of Erlang.

You only need to install Erlang if you compile ejabberd from source code.

And yes: ejabberd 2.1.3 works perfectly with all Erlang R12 and R13.

module compiling

Well, however I have installed win32 binary of ejabberd I will probably want to compile some modules (mod_logxml etc.) so I guess I still need the Erlang compiler.

Syndicate content