Thread

Hi all,

We recently upgraded from 1.6.4 to 1.6.7 on a site and some writers are now seeing all quotation marks (single and double) being escaped with backslashes when they submit content. This is happening via a SAEF; however I have not been able to validate whether the same thing would happen if they submitted directly via the control panel (these writers do not have access to the control panel).

We have also tried having other staff submit the same content (Word file -> paste into SAEF) and no problems arise. So there seems to be something specific to these users that is causing a problem—although it never did so before the upgrade.

Was there a change in the higher-ascii-characters-to-entities code between 1.6.4 and 1.6.7? Has anyone else experienced this (and resolved it)?

Many thanks,
Rob

Greetings Rob:

What are your settings at:  CP Home ›  Admin ›  Weblog Administration ›  Global Weblog Preferences for Automatically Convert High ASCII Text to Entities

-greg

Hi Greg—first thing I checked. That preference is set to ‘Yes’ and indeed seems to be working exactly as intended for the majority of submissions. This behavior is definitely new (post-upgrade from 1.6.4 to 1.6.7) and only seems to be affecting a minority of users.

Rob

Rob,

Are you using any typography plugins on your site, like Textile for example?

There have been a few EE Typography class tweaks according to changelog but what I would like you to do is to get your author(s) to write down the exact steps they use to submit an entry to your website. Are they copying and pasting? Are they entering it directly etc.

Hi John,

It’s a pretty varied workflow but the common thread is that authors (we have many) are copying and pasting into the SAEF. Sometimes this is from MS Word, sometimes other text editors.

We’re using the Legacy Typography plugin for the field in question. Is that possibly behind it? We only started to see this problem when we upgraded to EE 1.6.7 (at which point we started using the Legacy Typography plugin). We had been successfully using this workflow since 2006.

Thanks,
Rob

Which version/build of ExpressionEngine are you using? You can find that out at the bottom of any control panel page.

The current version is 1.6.7 and the build is 20090515.

If you haven’t upgraded to the newest version, please do so. This way we’ll both be using the same version/build for troubleshooting.

Hi Sue,

We upgraded to 1.6.8 build 20090723 over the weekend. We’re still seeing the problem persist. Anything you can do to help would be enormously appreciated.

I would mention that we are using the legacy typography plugin, rather than xhtml formatting, for the field(s) in question. Does that govern how higher ascii characters (like curly quotes being pasted in from MS Word) are treated?

Many thanks for any insight you can provide,
Rob

what extensions are you running?

-greg