Hi airfoil:
The FF error is likey caused by something else and it shouldn’t have anything to do with the other problem you are experiencing.
For the escaping problem, does it occur on al elements or just some of them? For non-admin users, all “dangerous” HTML nodes and attributes will be stripped or escaped (<script />, , etc.)
Godfrey
Thanks, Godfrey.
This situation is happening with site admin users, and has not been reported with other elements. That said, the users in question are working from a location in another state, and I’m only going by reports and what I’ve seen when I log in and look at the widget after they attempt to add HTML into the section widget.
I’m not actually suspecting the widget/plugin itself, since I can’t replicate the problem from my end – just wondering if anyone had experienced anything similar and had any ideas about where to start looking.
Thank again – I appreciate your response.
I’m seeing this too. In my case, I’m having any single-quote or double-quote escaped, by an admin user running Firefox on a Mac. I’m running FF on a PC and it works fine; any idea why it would work on one and not the other?
This is the code pre- and post-escaping. I am using single quotes here but it has exactly the same behavior with double-quotes around the parameters, which I believe is the correct way to do it:
PRE:
[featuredRacker
name='Joel Walker'
title='Linux Specialist / Cyclist'
linktext='View their Racker experience'
link='/joel-walker/'
image='/files/2010/02/img-racker1.jpg'
]
POST:
[featuredRacker
name=\'Joel Walker\'
title=\'Linux Specialist / Cyclist\'
linktext=\'View their Racker experience\'
link=\'/joel-walker/\'
image=\'/files/2010/02/img-racker1.jpg\'
]