I found the offending plugin: WP Facebook Open Graph protocol. It's being actively developed, so I would expect this issue to be resolved.
Thanks again! On Fri, Sep 21, 2012 at 8:09 PM, Brent Logan <[email protected]> wrote: > You're exactly right! I disabled *all* my plugins, went to the theme > editor, and the slashes are there. Now to enable them one by one and > find the offending plugin... > > I should have tried this on the default theme with no plugins before > making a report. Sorry... :-( > > But thanks for your help! > > On Fri, Sep 21, 2012 at 7:58 PM, Dion Hulse (dd32) <[email protected]> > wrote: >> Thanks for confirming >> >> I can't duplicate it though.. It could be a plugin conflict though, >> something is causing an extra stripslashes() to be run on the content. >> It could even be Javascript in the browser from a plugin, although there >> isn't many that would cause it. >> I'd be interested if you could duplicate it on a clean installation.. >> >> On 22 September 2012 12:52, Brent Logan <[email protected]> wrote: >> >>> I'm using the theme editor that is accessed by clicking or hovering >>> over Appearance and then clicking Edit. I'm not using Jetpacks CSS >>> editor. >>> >>> I used FTP + and editor to replace all the slashes, saved the CSS >>> file, and confirmed proper appearance on my blog. Then I returned to >>> the theme editor to look at the CSS file, and they don't appear. I >>> believe the slashes are being stripped when the file is opened and >>> displayed by editor and then saving the file completes their deletion. >>> >>> On Fri, Sep 21, 2012 at 7:26 PM, Dion Hulse (dd32) <[email protected]> >>> wrote: >>> > WordPress's Theme editor seems to work as expected, but the Jetpack >>> Custom >>> > CSS editor seems to show the problem. >>> > >>> > Can you confirm which one you're using? (Hint: WordPress editor is >>> > 'Editor', Jetpack is 'Edit CSS') >>> > >>> > On 22 September 2012 12:14, Brent Logan <[email protected]> wrote: >>> > >>> >> I'm not sure when the change took place, but editing a CSS file using >>> >> the theme editor strips the slashes from CSS escaped characters. >>> >> >>> >> For example: >>> >> >>> >> .next-comment-link a:before{content:"\2190"} >>> >> >>> >> loses the \ before 2190. >>> >> >>> >> It does make the blog look a little funny. I guess that's one way to >>> >> stop people from using the theme editor. ;-) >>> >> >>> >> -Brent >>> >> _______________________________________________ >>> >> wp-testers mailing list >>> >> [email protected] >>> >> http://lists.automattic.com/mailman/listinfo/wp-testers >>> >> >>> > _______________________________________________ >>> > wp-testers mailing list >>> > [email protected] >>> > http://lists.automattic.com/mailman/listinfo/wp-testers >>> _______________________________________________ >>> wp-testers mailing list >>> [email protected] >>> http://lists.automattic.com/mailman/listinfo/wp-testers >>> >> _______________________________________________ >> wp-testers mailing list >> [email protected] >> http://lists.automattic.com/mailman/listinfo/wp-testers _______________________________________________ wp-testers mailing list [email protected] http://lists.automattic.com/mailman/listinfo/wp-testers
