mirror of
https://github.com/processone/ejabberd.git
synced 2024-11-30 16:36:29 +01:00
52 lines
1.8 KiB
Plaintext
52 lines
1.8 KiB
Plaintext
|
|
||
|
Release Notes
|
||
|
ejabberd 2.1.2
|
||
|
|
||
|
ejabberd 2.1.2 is the second bugfix release in ejabberd 2.1.x branch.
|
||
|
|
||
|
ejabberd 2.1.2 includes several bugfixes.
|
||
|
More details of those fixes can be retrieved from:
|
||
|
http://redir.process-one.net/ejabberd-2.1.2
|
||
|
|
||
|
The new code can be downloaded from ejabberd download page:
|
||
|
http://www.process-one.net/en/ejabberd/
|
||
|
|
||
|
|
||
|
The major changes are:
|
||
|
|
||
|
* Core
|
||
|
- Close sessions that were half connected
|
||
|
- Fix SASL PLAIN authentication message for RFC4616 compliance
|
||
|
- Fix support for old Erlang/OTP R10 and R11
|
||
|
- Return proper error (not 'conflict') when register is forbidden by ACL
|
||
|
- When ejabberd stops, send stream close to clients
|
||
|
|
||
|
* ejabberdctl
|
||
|
- Check for EGID in ejabberdctl command
|
||
|
- Command to stop ejabberd informing users, with grace period
|
||
|
- If there's a problem in config file, display config lines and stop node
|
||
|
|
||
|
* MUC
|
||
|
- Kick occupants with reason when room is stopped due to MUC shutdown
|
||
|
- Write in room log when a room is created, destroyed, started, stopped
|
||
|
|
||
|
* PubSub and PEP
|
||
|
- Don't call gen_server on internal event (improves performance and scalability)
|
||
|
- Fix duplicate SHIM header in Pubsub message
|
||
|
- Notification messages of Pubsub node config change contained a SHIM header
|
||
|
- SubID SHIM header missing in Pubsub message with multiple
|
||
|
subscriptions on the same node
|
||
|
- PEP: last published item not sent from unavailable users when the
|
||
|
subscription is implicit (XEP-0115)
|
||
|
- pep_mapping not working due to Node type mismatch
|
||
|
|
||
|
* WebAdmin
|
||
|
- If big offline message queue, show only subset on WebAdmin
|
||
|
- Support in user list page of WebAdmin when mod_offline is disabled
|
||
|
|
||
|
|
||
|
Bug reports
|
||
|
|
||
|
You can officially report bugs on ProcessOne support site:
|
||
|
http://support.process-one.net/
|