[rt-users] Problem : A custom field edited via REST will be disabled

[Kevin Falcone]

On Fri, Feb 14, 2014 at 08:02:58PM +0100, Sylvain Auguy wrote:
>    To follow up with my investigations, I saw that the HTML spec stipulates that a new line in a
>    form content will be represented by "CR LF" pairs.
>    http://www.w3.org/TR/html4/interact/forms.html#h-17.13.4.1
>    So, there seems to be no way to edit multiple fields via REST called by an HTML form, because
>    it will always send newlines as \r\n and that RT will recognize only \n as a new line. Or...
>    Am I missing something ?

You're only sending \r, if you sent valid POST data, RT would
understand it.

>    Would it be possible to make a patch for this ?

Hardcoding a form to submit random stuff to the RT REST interface is
begging for trouble (see your current state).

You're also testing against RT 3.8.4, which currently gets nothing but
security and critical bugfixes and will be end of lifed shortly.

http://bestpractical.com/rt/release-policy.html

-kevin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 235 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20140214/4d585b00/attachment.sig>