ejabberd - Comments for "MUC history in reverse order (newest at top)"

dp_wiz wrote: I've been

mfoss — Sat, 11 Jun 2011 14:48:57 +0000

dp_wiz wrote:

I've been running on 2.1.6 and now installed 2.1.8 from downloads (which strangely identifies itself as 2.1.7 «running on that node») and everything now is in correct order.

Ah, now I noticed this ticket: https://support.process-one.net/browse/EJAB-1374

Regarding the "2.1.7" misleading text: right, that's a mistake in the code. Don't worry.

I've been running on 2.1.6

dp_wiz — Fri, 10 Jun 2011 05:56:11 +0000

I've been running on 2.1.6 and now installed 2.1.8 from downloads (which strangely identifies itself as 2.1.7 «running on that node») and everything now is in correct order.

Config were pretty generic:

  {mod_muc,      [
                  %%{host, "conference.@HOST@"},
                  {access, muc},
                  {access_create, muc_create},
                  {access_persistent, muc_create},
                  {access_admin, muc_admin}
                 ]},

i can reproduce it in

rose_panhl — Wed, 08 Jun 2011 09:24:28 +0000

i can reproduce it in ejabberd 2.1.6

dp_wiz wrote: that was

mfoss — Tue, 07 Jun 2011 08:52:41 +0000

dp_wiz wrote:

that was working before

In what ejabberd version do you remember that MUC history over BOSH worked correctly for you?

What ejabberd version do you have installed now that sends history reversed?

Try with Psi, Jabbim, Tkabber, or other TCP client, do you receive history reversed?

Try with Gajim, configure it to use BOSH, do you receive history reversed?

Show your mod_muc configuration here.

It is. Here's a complete dump

dp_wiz — Mon, 06 Jun 2011 11:55:26 +0000

It is. Here's a complete dump of a BOSH response received while joining the conference: http://pastebin.com/L0gZ31WL
Notice the delay stamps:

stamp="2011-06-06T11:03:32Z"
stamp="2011-06-06T11:03:23Z"
stamp="2011-06-06T11:02:43Z"
stamp="2011-06-06T11:02:30Z"

I've tried with ejabberd

mfoss — Mon, 06 Jun 2011 09:03:04 +0000

I've tried with ejabberd 2.1.7/2.1.8, Tkabber TCP connection, Gajim BOSH connection, a MUC new room.

I send messages like "1", "2", "3". Then I open the XML Raw Window of each client, and reconnect to the room. Both clients get the XML messages in the correct order, and they display them correctly.

Check the TCP/XML/XMPP traffic: does your custom-developed client really receive always all the room history in reverse order?