Opened 8 years ago

Closed 8 years ago

Last modified 7 years ago

#6236 closed defect

Contact Grouping ignored with Openfire Roster Sharing

Reported by: Tobi Owned by: nwalp
Milestone: Component: XMPP
Version: 2.4.2 Keywords:
Cc: lemsto

Description

Hi,

not shure if this ist the right Place but I found no other solution. I use pidgin 2.4.3 as a client for openfire 3.5.0 authenticating users against LDAP. I configured openfire to share some usergroups to all users/add them to their contact list. Some users are in more than one group. When I group them in pidgin every time I start pidgin again they are again not grouped but apart in multiple groups. Example: User A is in group 1 and group 2. I group the together as user A in group 1 but when I restart pidgin user A is in group 1 and group 2 and not grouped together. It seems for me openfire everytime I connect overwirte the pidgin settings or pidgin is not able to know that this users where grouped together last start. I'm not sure if this is an pidgin or an openfire problem. Thanks for your help. Tobi

Her are the Logs during grouping contacts:

(16:01:47) jabber: Sending (ssl): <iq type='set' id='purple32f092a0'><query xmlns='jabber:iq:roster'><item jid='userA@server' name='UserA'><group>group1</group></item></query></iq>
(16:01:47) jabber: Recv (ssl)(312): <iq type="error" id="purple32f092a0" to="me@server"><query xmlns="jabber:iq:roster"><item jid="userA@server" name="UserA"><group>group1</group></item></query><error code="406" type="modify"><not-acceptable xmlns="urn:ietf:params:xml:ns:xmpp-stanzas"/></error></iq>
(16:01:48) util: Writing file prefs.xml to directory C:\Dokumente und Einstellungen\me\Anwendungsdaten\.purple
(16:01:48) util: Writing file C:\Dokumente und Einstellungen\me\Anwendungsdaten\.purple\prefs.xml
(16:01:52) util: Writing file blist.xml to directory C:\Dokumente und Einstellungen\me\Anwendungsdaten\.purple
(16:01:52) util: Writing file C:\Dokumente und Einstellungen\me\Anwendungsdaten\.purple\blist.xml

Change History (7)

comment:1 Changed 8 years ago by deryni

  • pending changed from 0 to 1

You are attempting to move the shared roster users from the group the server places them in to a different group, correct? If so that is not something the Openfire shared roster implementation allows you to do (which is why in your debug output you see an error response). Error responses to things like this are unfortunately not something pidgin handles well at the moment so while it looks like the move/join was successful it wasn't and will revert back next time. There is nothing we can do about this (other than remember the move locally, as opposed to on the server, which isn't something we want to be doing). This is one of the many possible problems with shared roster support.

comment:2 Changed 8 years ago by Tobi

  • pending changed from 1 to 0

If I tried to place users in different groups than the group the server places them I did it unknowingly. I just want to group the users which are in more than one group to one cantact. Like I would do if I have a buddy with multiple accounts (icq, msn, so on) and group them in one. But maybe when I do this pidgin tries to move the contact to the group where it is still a member an is shown as a seperate user. It is a bit confusing to explain and I hope my english is good enough to this. My favourite behaviour would be that pidgin does not send anything to the server when I group my buddies but stores this information only locally ans restores it at restart. How does this grouping buddies into contacts works when there are multiple protocols? Does pidgin send group information to all servers? Anyway many thanks for the fast answer an good to read that there is still worked on this. Tobi

comment:3 Changed 8 years ago by deryni

  • pending changed from 0 to 1

"I just want to group the users which are in more than one group to one cantact." <- That means you tried to move buddies between groups, which means you tried to move the shared roster buddies from the group the server placed them in to another group. That is *exactly* what I was explaining cannot be done. pidgin cannot group buddies that are in different groups without moving them all into one group. No contact-grouping information is sent to any of the IM servers, but the buddy list group information is synchronized with the server so that as much information as possible is stored there.

comment:4 Changed 8 years ago by trac-robot

  • pending changed from 1 to 0
  • Status changed from new to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

comment:5 follow-up: Changed 7 years ago by lemsto

Hey there,

I too have this issue with contact groups using Pidgin 2.6.5 (and earlier 2.6 versions) and OpenFire 3.6.2.

This is our corporate IM here and most of people are using the Spark XMPP client. A group containing all people from the company is provided by the server.

Dragging people from that group to other groups works well with the Spark client. In fact it seems to create a copy of the contact to the new group, instead of moving it as Pidgin does.

Is it possible to make a difference between user defined groups and server provided groups ? So moving contact from a group to another wouldn't have the same behaviour depending the source/target groups ?

I'd say that no contacts can be added/removed from server provided groups ...

Thanks in advance for answering,

Regards.

comment:6 in reply to: ↑ 5 ; follow-up: Changed 7 years ago by darkrain42

Replying to lemsto:

Hey there,

I too have this issue with contact groups using Pidgin 2.6.5 (and earlier 2.6 versions) and OpenFire 3.6.2.

This is our corporate IM here and most of people are using the Spark XMPP client. A group containing all people from the company is provided by the server.

Dragging people from that group to other groups works well with the Spark client. In fact it seems to create a copy of the contact to the new group, instead of moving it as Pidgin does.

Is it possible to make a difference between user defined groups and server provided groups ? So moving contact from a group to another wouldn't have the same behaviour depending the source/target groups ?

I'd say that no contacts can be added/removed from server provided groups ...

Thanks in advance for answering,

Regards.

You can't override the fact Pidgin treats dragging as a move, but if you go to Buddies->Add Buddy and add people to a second group, those changes should be persisted across restarts of Pidgin.

If they're not, please file a new ticket and attach the output of the Help->Debug Window when you add the second buddy.

comment:7 in reply to: ↑ 6 Changed 7 years ago by lemsto

Replying to darkrain42:

Replying to lemsto:

Hey there,

I too have this issue with contact groups using Pidgin 2.6.5 (and earlier 2.6 versions) and OpenFire 3.6.2.

This is our corporate IM here and most of people are using the Spark XMPP client. A group containing all people from the company is provided by the server.

Dragging people from that group to other groups works well with the Spark client. In fact it seems to create a copy of the contact to the new group, instead of moving it as Pidgin does.

Is it possible to make a difference between user defined groups and server provided groups ? So moving contact from a group to another wouldn't have the same behaviour depending the source/target groups ?

I'd say that no contacts can be added/removed from server provided groups ...

Thanks in advance for answering,

Regards.

You can't override the fact Pidgin treats dragging as a move, but if you go to Buddies->Add Buddy and add people to a second group, those changes should be persisted across restarts of Pidgin.

If they're not, please file a new ticket and attach the output of the Help->Debug Window when you add the second buddy.

As you said those changes are persistent. Tanks for your help ! I have to admit that I didn't try to add new contacts I already had.

I understood that Pidgin treats dragging as a move. But even using menus, there is no way to simply copy a contact. Anyway, I managed to populate my groups ...

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!