THANKS ALL!
Changing that column to LONGBLOB fixed it for me. Thanks a lot!
-Original Message-
From: Donovan Young [mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, September 13, 2006 3:44 PM
To: Peake, Jeremy
Cc: rt-users@lists.bestpractical.com
Subject: RE
>$MaxAttachmentSize (make sure it's big enough) $TruncateLongAttachments
(make sure it's undef) $DropLongAttachments (make sure it's undef)
I checked that out, $MaxAttachSize is 10 megs and truncate and drop are
both undef.
Also saw an earlier post of same issue, and tried reinstalling Perl
(5.8
Title: Attachments getting mangled
Not even sure where to look to troubleshoot this one. When a users emails in a new ticket request, if there is an attachment to the email, that attachment gets mangled in RT, and cannot be viewed by the admin.
I can see there is an attachment to the ticket
remy,
The MySQL client library has changed.
Recompiling DBD::mysql solved the same problem for me.
David
Peake, Jeremy wrote:
> ooops, nevermind. it doesn't work after the downgrade. I can "OPEN"
> a ticket. but cannot &q
Title: Upgraded MySQl to 4.1.21 - now getting "transactions not supported"
ooops, nevermind. it doesn't work after the
downgrade. I can "OPEN" a ticket. but cannot "TAKE" "COMMENT"
"REPLY" "RESOLVE"
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peake,
JeremySent: Tuesda
Title: Upgraded MySQl to 4.1.21 - now getting "transactions not supported"
I downgraded to MySQL 4.1.20 and it works
fine.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Peake,
JeremySent: Tuesday, August 15, 2006 8:30 AMTo:
rt-users@lists.bestpractical.comSubject: [rt-use
Title: Upgraded MySQl to 4.1.21 - now getting "transactions not supported"
After the MySQL upgrade, it appears the Rt database was set to myisam. I changed it back to innodb, restarted Mysql and the web server. Still getting this error when I try to comment, reply or resolve any ticket. An
