ejabberd - Comments for "Shared roster groups doesn't work"

same problem

avjabber — Mon, 13 Feb 2006 02:12:30 +0000

I have the same problem with 10.0.0 on a fedora 4 platform. did you find out what it is. my users are all registerd under abc@localhost, def@localhost ect

It started to work by itself after 15 mins...strange

Shared Roster not working.

alive88 — Tue, 06 Sep 2005 05:46:29 +0000

When I setup SHARED rosters for a valid Internet domain -they work. But when I change to an intranet domain name they stop working.

Any ideas?

WORKS
Group1
member@validca.ca
member2@validca.ca

DOES NOT WORK
Group1
member@validca.mytld
member2@validca.mytld

I did a test tonight for a valid internet domain that resolves to an intranet IP - and it didn't work.

If this is a known issue. Otherwise I will spend some time to figure out exactly what is happening.

It still does not work

Kingedgar — Mon, 25 Jul 2005 06:50:49 +0000

I have the exact same problems.

Each user can only see 1st user in first group listed. The rest go unfiled.

Tested with Gaim, Tkabber, and jwchat.

so if

group1=xxxx
members= test1@test.host
test2@test.host
Displayed groups= yyyy
xxxx

group2=yyyy
memers= test3@test.host
test4@test.host
Displayed groups= xxxx
yyyy

test1 sees it like this

xxxx
test1@test.host
unfiled
test2@test.host
test3@test.host
test4@test.host

And the same for the rest. They only see the first member of the first group that they are not assigned to.

Did I just confuse everyone? I can provide screenshots if needed.

Shared Roster Oddities

bbrazell — Tue, 12 Jul 2005 14:02:45 +0000

I'm seeing some unusual issues with shared rosters. Others have reported similar problems. Here is what I'm getting. Running ejabberd v0.9.1.

Created a group as follows:

Group Name: test
Name: Test Group
Description: This is a test group.
Members:
bill@fqdn.com
roger@fqdn.com
Displayed Groups: test

When I login, I can see the group called Test Group. The only member I see in the group is bill; roger is not shown in the Test Group. I tried this with a couple of other groups and they all behave the same. Not sure what's going on.

Additionally, I thought I'd delete the groups and start over. After deleting them, they still appear within the client. I even restarted the node but they still persist. Clients tested were GAIM 1.4.0 and Pandion 2.1.2.

it should not be a problem

mfoss — Wed, 15 Jun 2005 17:29:53 +0000

'one per line' means that the JIDs must be separated by Carriage Return characters. So the fact that your browser shows you the JIDs broken is not a problem, as long as they aren't actually broken.

Try using a group name lowercase: lp instead of LP