MUCed Up In a Mine Field
- user warning: Table 'nolan.comments' doesn't exist
query: SELECT COUNT(*) FROM comments WHERE nid = 116 AND status = 0 in /home/sneakin/web/nolan.eakins.net/includes/database.mysql.inc on line 120.
- user warning: Table 'nolan.comments' doesn't exist
query: SELECT c.cid as cid, c.pid, c.nid, c.subject, c.comment, c.format, c.timestamp, c.name, c.mail, c.homepage, u.uid, u.name AS registered_name, u.picture, u.data, c.score, c.users, c.thread, c.status FROM comments c INNER JOIN users u ON c.uid = u.uid WHERE c.nid = 116 AND c.status = 0 GROUP BY c.cid, c.pid, c.nid, c.subject, c.comment, c.format, c.timestamp, c.name, c.mail, u.picture, c.homepage, u.uid, u.name, u.picture, u.data, c.score, c.users, c.thread, c.status ORDER BY c.thread DESC LIMIT 0, 50 in /home/sneakin/web/nolan.eakins.net/includes/database.mysql.inc on line 120.
Submitted by sneakin on Thu, 2005/03/03 - 16:20.
Jabber | Psi
I thought I would do some quick testing on my working copy of Psi to figure out what needs to be done next for MUC. I fired up the affiliation editor, and as expected I get an error message due to my query for affiliations that are 'none'. The message box is essentially empty and I was wondering why since I handle error stanzas in the Task. Looking at the XML that I received mu-conference (am I correct that this is what j.org is using?) there error stanza was tucked into an <item> element. I then checked JEP-0045 to see where the error element was supposed to appear. Turns out mu-conf isn't working correctly—again.
I have to ask, must I support these "features" or go with the JEP (which needs some work, or to be phased out in favor of MUC+)?
|
