Formit and bizarre UTF-8 input issue

I have a form that has a custom hook that I dump into SalesForce. I am experiencing a strange issue with character encoding.

I used the debug to see why that field was getting truncated by SalesForce.
---
debug result
---

---
debug result
---

It seams if forcing SalesForce to remove anything after that character. No issues with

Any help would be greatly appreciated.

The only thing I am doing now is Formit validation of strip^'^ which seams to help but I really want all the info to just go into the field.

Apparently they have some kind of incoming data validation that requires incoming single quotes be escaped.

https://developer.salesforce.com/forums/?id=906F000000093dmIAA

The latest FormIt versions have a security feature in it. The field input is handled by htmlspecialchars to avoid XSS by default. To suppress this for a special field, you have to add the allowSpecialChars validator on that field.



That way the special chars (Quotes, <, > and &) in that field are not replaced with their entities.

Quote from: sottwell at Apr 07, 2016, 12:15 AM

Apparently they have some kind of incoming data validation that requires incoming single quotes be escaped.

https://developer.salesforce.com/forums/?id=906F000000093dmIAA

I was trying to escape the data in PHP but not having much luck at all or I was handling it all wrong (most likely wrong handling ).

Quote from: Jako at Apr 07, 2016, 01:16 AM

The latest FormIt versions have a security feature in it. The field input is handled by htmlspecialchars to avoid XSS by default. To suppress this for a special field, you have to add the allowSpecialChars validator on that field.

[[!FormIt? &validate=`message:allowSpecialChars`]]

That way the special chars (Quotes, <, > and &) in that field are not replaced with their entities.

That worked perfectly!!! Thank you Jako I could not find that piece anywhere online (https://rtfm.modx.com/extras/revo/formit/formit.validators)

It's there, in the grid of Built-In Validators

I completely overlooked that. Thank you. Says it's on by default but apparently not.

I have added that allowSpecialChars option today to the docs, after writing the post. So maybe it was not there, when you looked for it.

Quote from: rcarnrick at Apr 07, 2016, 01:11 PM

Says it's on by default but apparently not.

Fixed in the docs, thanks.