HistoricalFAQ

Introduction

This is historical questions from main FAQ that are not that frequent any more.

History

Q: Why do I need perl 5.8.3 or greater?

A: Perl 5.8.{0,1,2} has a bug in the 'join' command code that cause attachment corruptions under some magic conditions. Additionally, perl 5.8.0 appears to suffer from some sort of email address parsing bug. You have to decide whether to be immmune to this bugs from the start, or wait until the bugs show themself and destroy your valuable data. See also next question and AccentBug.

---

Q: I've upgraded perl, but mod_perl still uses old perl binary. Why?

A: You have to rebuild mod_perl too. Please read notes for mod_perl users at CompilingPerl.

---

Q: Attachments to emails with a space in the filename (ie. Hockey Photo.jpg) are not accessible from the Web Interface. When you attempt to load the image from the Web Interface it add the escape character %20 to the URL but is unable to load the image. I attempted to add a segment of perl to rename the attachment replacing " " with "_" but am unsure of what file it should go into (tried Attachment.pm). This is a new installation. Anybody have a fix for this issue?

A: Use MailingLists for anything like this!!! The wiki is not for asking questions, is not for discussing anything, is not for commenting. The wiki is for delivering ready to read and use material.

---

Q: My attachments are corrupted?

A: In most cases it's perl/UTF bug. Update minimum to perl5.8.3 or greater and rt3.0.8 or greater. Also don't forget to look in the mailing list archives for more info.

---

Q: I'm using MySQL, and whenever I use the web interface to make a comment, it makes a blank comment before the one with content

A: Your tables MyISAM tables, and are hence not transactional. This happens because MySQL silently creates MyISAM tables when asked to create InnoDB tables, if your build of MySQL has InnoDB disabled or not compiled in. Upgrade your tables to InnoDB tables to fix this; see http://dev.mysql.com/doc/mysql/en/converting-tables-to-innodb.html for instructions.