tag:help.lighthouseapp.com,2008-09-20:/discussions/api-developers/72-not-getting-body-and-body-html-attributes-for-ticketsLighthouse: Discussion 2012-06-29T22:10:45Ztag:help.lighthouseapp.com,2008-09-20:Comment/469822009-02-06T20:42:57Z2009-02-06T20:42:57ZNot getting body and body-html attributes for tickets<div><p>I'm still seeing this. Is this expected or a bug?</p></div>peejatag:help.lighthouseapp.com,2008-09-20:Comment/469822009-03-14T14:34:28Z2009-03-14T14:34:28ZNot getting body and body-html attributes for tickets<div><p>It's a workaround for a weird bug. Basically, people were
fetching tickets from the API, changing something other than body,
and that body attribute would get set as the most recent comment.
Perhaps I should send <code>original_body</code> and
<code>latest_body</code> then?</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/469822009-03-16T23:07:12Z2009-03-16T23:07:12ZNot getting body and body-html attributes for tickets<div><p>I'm not sure I understand the bug, but yes, that would be
helpful.</p></div>peejatag:help.lighthouseapp.com,2008-09-20:Comment/469822009-03-16T23:38:32Z2009-03-16T23:38:32ZNot getting body and body-html attributes for tickets<div><p>The ruby library pulls the data when you do
<code>Ticket.find</code>. When saved, it sends all the data to the
Lighthouse update action. Lighthouse interprets the body as a new
comment (it's how the HTML form essentially works). If I move the
fields out to something not named #body, then they'll be ignored.
I'll do this as soon as I can... though it will require some
Lighthouse downtime. I'm thinking Thursday night (watch Lighthouse
for the official announcement).</p></div>Ricktag:help.lighthouseapp.com,2008-09-20:Comment/469822009-03-17T14:37:47Z2009-03-17T14:37:47ZNot getting body and body-html attributes for tickets<div><p>That would be awesome. Thanks!</p></div>peeja