Bug tracker

This ticket has been moved to our new tracker. Open Ticket PHPBB3-378 now.

Jabber PM Notification special chars (fix completed in vcs)

Since the Jabber notification is now working properly after closing this bug, I've been playing with the feature a little bit.
There is still a little bug. If your are using specific characters in the subject when writing a PM it won't be submitted.

SEND

Code: Select all
<message to='XXXX@jabber.freenet.de' type='normal' id='normal_1145370013'>
<body>Hello XXXX,

You have received a new private message from &quot;xern&quot; to your account on &quot;xxx.de&quot; with the following subject:

[b]&Ouml;[/b]

You can view your new message by clicking on the following link:

http://XXX.de:443/phpBB2/ucp.php?i=pm&amp;mode=unread

You have requested that you be notified on this event, remember that you can always choose not to be notified of new messages by changing the appropriate setting in your profile.

--
Thanks, The Management</body>
</message>


RECIEVE

Code: Select all
<stream:error>Invalid XML</stream:error>



I tried to highlight the problematic part. If the subject contains a character like Ö,Ä,Ü,§
the message won't be processed by the server. I couldn't test all characters, sometimes & is problematic, too.

One way to solve this issue would be not subitting the subject which can be defined by the sender. The best solution is to make the xml code full compatible with xml, by preprocessing/filtering those special characters.

Comments / History

Posted by secdo on Apr 18th 2006, 14:36

Sorry highligthing didn't work. Subject of the PM only contained this char: Ö
which has been processed as:
&Ouml;

this generates the xml stream error.

Posted by secdo on Apr 18th 2006, 14:52

Okay hopefully the last completition. The bug can be reproduced by sending Instant Messages via the

/phpBB2/memberlist.php?mode=contact&action=jabber&u=2

function. Since those messages can also contain those special chars, they're not send processed by the jabber server, also the user gets a "successfully sent" message.

Posted by Acyd Burn (Server Manager) on Apr 28th 2006, 12:45

Nils... maybe you are able to have a short look regarding the correct encodings. Wink

Linked ticket with changeset: r6034

Action performed by naderman (Development Team Leader) on Jun 9th 2006, 23:46

Posted by naderman (Development Team Leader) on Jun 9th 2006, 23:48

Can you check again with latest CVS please and report back if any problem still exists?

Ticket details

Related SVN changesets