Encoded HTML entities

[Thomas Legg]

I have an installation of speeqe and have issues with the web clients
producing encoded HTML entities in the chat.

Items like ',<,>,& are being escaped to their html encodings like
&amp; and &#39; and that is being delivered even to IM clients.

If I use the php XMPPCHAT as the front end to strophe/ejabberd, this
doesn't happen.

If I use an IM client to chat in the MUC and use these characters they
display properly back to the web client, so it's only on the speeqe
input.

Has anyone else seen this before?

Thomas Legg

--
You received this message because you are subscribed to the Google Groups "speeqe" group.
To post to this group, send email to spe...@googlegroups.com.
To unsubscribe from this group, send email to speeqe+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/speeqe?hl=en.

[Nathan Zorn]

I am sure the code that did the escaping was there for an old strophe bug, but is now no longer needed.  I removed it in the master branch.

[Tom legg]

Beautiful. Thanks. That was it.

Somehow the rsync between git and deployment hadn't updated the chat.js
properly and text = Speeqe.htmlentities(message); was still hanging around.

Tom Legg

On 7/05/10 5:47 AM, Nathan Zorn wrote:
> The change was in chat.js and I removed the line that called
> Speeq.htmlentities. What client do you see the escaped characters in?
>
> On Thu, May 6, 2010 at 12:16 AM, Tom legg <tjl...@gmail.com
> <mailto:tjl...@gmail.com>> wrote:
>
> I'm using the master branch. Just updated from git and the
> problem is still there.
>
> Where exactly was this code? client.js? What should I be looking for?
>
> Tom Legg

>
>
> On 6/05/10 8:47 AM, Nathan Zorn wrote:
>
> I am sure the code that did the escaping was there for an old
> strophe bug, but is now no longer needed. I removed it in the
> master branch.
>
> On Tue, May 4, 2010 at 8:58 PM, Thomas Legg <tjl...@gmail.com

> <mailto:tjl...@gmail.com> <mailto:tjl...@gmail.com