changeset 25066:256fbe98f6be

The jabber_register_parse function was looking for the <x> node as a child of the <iq> node instead of the <query> node. (See Chs 4 & 5 of XEP-0077) Somebody (maybe it'll be me?) should probably check that the code for these two cases does what it's supposed to, since I don't think it would have run before now. It also looks like the precedence may be wrong (See Ch 6).
author Elliott Sales de Andrade <qulogic@pidgin.im>
date Sat, 07 Feb 2009 23:45:18 +0000
parents bba924f14a6b
children 2035b8164aca
files libpurple/protocols/jabber/jabber.c
diffstat 1 files changed, 2 insertions(+), 2 deletions(-) [+]
line wrap: on
line diff
--- a/libpurple/protocols/jabber/jabber.c	Fri Feb 06 14:23:25 2009 +0000
+++ b/libpurple/protocols/jabber/jabber.c	Sat Feb 07 23:45:18 2009 +0000
@@ -1021,11 +1021,11 @@
 		}
 	}
 	
-	if((x = xmlnode_get_child_with_namespace(packet, "x", "jabber:x:data"))) {
+	if((x = xmlnode_get_child_with_namespace(query, "x", "jabber:x:data"))) {
 		jabber_x_data_request(js, x, jabber_register_x_data_cb, g_strdup(from));
 		return;
 
-	} else if((x = xmlnode_get_child_with_namespace(packet, "x", "jabber:x:oob"))) {
+	} else if((x = xmlnode_get_child_with_namespace(query, "x", "jabber:x:oob"))) {
 		xmlnode *url;
 
 		if((url = xmlnode_get_child(x, "url"))) {