I have installed RT3.0.6 and RTFM2.0.1 with FastCGI on Solaris +
Apache 1.3 + Perl 5.8.2 to replace a 2.0 installation. This seems to
be working well, except for the CLI. For some reason it is
interpreting the command as a ticket id. This is after fixing the
problem with the extra newline in RTFM. (I couldn’t find a mention of
this problem in the archives.)
Any suggestions for a fix? My perl is unfortunately quite bad.
[11:10] vuori ~% rt edit ticket/5 set status=deleted
POST http://localhost:27081/REST/1.0/edit
Content-Length: 101
Content-Type: multipart/form-data; boundary=xYzZY
Cookie: RT_SID=XXX
–xYzZY
Content-Disposition: form-data; name=“content”
status: deleted
id: ticket/5
–xYzZY–
HTTP/1.1 200 OK
Connection: close
Server: Apache/1.3.27 (Unix) mod_fastcgi/2.4.2
Content-Type: text/plain; charset=ISO-8859-1
Client-Date: Mon, 01 Dec 2003 11:14:19 GMT
Client-Peer: 127.0.0.1:27081
Client-Response-Num: 1
Client-Transfer-Encoding: chunked
RT/3.0.6 200 Ok
Unknown object type: edit
status: deleted
id: ticket/5
Valtteri Vuorikoski vuori@magenta.net
MagentaSites Oy
I have installed RT3.0.6 and RTFM2.0.1 with FastCGI on Solaris +
Apache 1.3 + Perl 5.8.2 to replace a 2.0 installation. This seems to
be working well, except for the CLI. For some reason it is
interpreting the command as a ticket id. This is after fixing the
problem with the extra newline in RTFM. (I couldn’t find a mention of
this problem in the archives.)
Any suggestions for a fix? My perl is unfortunately quite bad.
The CLI saw signifcant improvements for 3.0.7 (and even more for 3.0.8,
but that’s not out yet
But you’re likely being bitten by the fact that
/opt/rt3/share/html/Callbacks/RTFM/autohandler/Default
has a newline it shouldn’t have.
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.
Jesse Vincent jesse@bestpractical.com writes:
The CLI saw signifcant improvements for 3.0.7 (and even more for 3.0.8,
but that’s not out yet
But you’re likely being bitten by the fact that
/opt/rt3/share/html/Callbacks/RTFM/autohandler/Default
has a newline it shouldn’t have.
I already removed the only spare newline that I could see, alas that only
fixed the “malformed response” error that I got first. It is still
thinking that “edit” is an object and I get
Unknown object type: edit
priority: 3
id: ticket/5
and nothing happens to ticket 5.
Valtteri Vuorikoski vuori@magenta.net
MagentaSites Oy
Jesse Vincent jesse@bestpractical.com writes:
The CLI saw signifcant improvements for 3.0.7 (and even more for 3.0.8,
but that’s not out yet
But you’re likely being bitten by the fact that
/opt/rt3/share/html/Callbacks/RTFM/autohandler/Default
has a newline it shouldn’t have.
I already removed the only spare newline that I could see, alas that only
fixed the “malformed response” error that I got first. It is still
thinking that “edit” is an object and I get
Unknown object type: edit
priority: 3
id: ticket/5
and nothing happens to ticket 5.
And there’s a fastcgi issue we’ve fixed in the core. Try 3.0.8pre1?
Request Tracker... So much more than a help desk — Best Practical Solutions – Trouble Ticketing. Free.