Ok my RT version is not supported so I don't demand you to solve this
particular case. However, I think there is a problem in the way RT parses
those values without handling correctly the new lines.
To support my position, I will describe again what I do.
I use the following to send a form with a
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
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
Now I can see that the value in the database for a customer field edited by
rest is, for instance, 'my value\r' instead of 'my value'
The REST query is made by an html form with an input like this :
However, when I analyze the HTML POST Data, I get
content=field1%3Avalue1*%0D%0A*field2%3Avalue
On Mon, Feb 10, 2014 at 02:16:50PM +0100, Sylvain Auguy wrote:
>Ok my bad... It does as you said Kevin, but I still have a problem. The
> new customer field
>values are not recognized properly by the pages Modify.html and
> ModifyAll.html and it acts as
>if these fields were without a
Thanks Kevin
This is the behavior I was expecting, except that in my case, it adds a new
row with the field "disabled = 1"
Is it a known bug that has been solved in a later version ?
Sylvain
2014-02-07 17:51 GMT+01:00 Kevin Falcone :
> On Fri, Feb 07, 2014 at 11:05:04AM +0100, Sylvain Auguy wr
On Fri, Feb 07, 2014 at 11:05:04AM +0100, Sylvain Auguy wrote:
>When I edit a custom field via REST, the associated
> "ObjectCustomFieldValue" will, by default,
>appear as disabled in the database.
>Is there any reason for that ? How can I avoid it ?
>I use RT 3.8.4.
When you upda
Hi,
When I edit a custom field via REST, the associated
"ObjectCustomFieldValue" will, by default, appear as disabled in the
database.
Is there any reason for that ? How can I avoid it ?
I use RT 3.8.4.
Sylvain
