Extra blank comment added!

RT Users
1

Hi List

I have just upgraded to 3.2.0 from 3.0.9 and almost everything seems to
work fine. When I make a comment or reply to a case, i get a blank
history entry first and then the next entry with the actual comment/reply.

Any ideas ?

Thanks in advance.
Kim Thostrup

2

I have just upgraded to 3.2.0 from 3.0.9 and almost everything seems to
work fine. When I make a comment or reply to a case, i get a blank
history entry first and then the next entry with the actual comment/reply.
You are most probably using a MySQL server that doesn’t support the
InnoDB table type; the tables are falling back to MyISAM, which is
non-transactional. The “scrips preview” on Update.html tries to start a
transaction, commit a comment, and then roll it back. Without
transactions, this results in a net empty comment.
For now, the solutions are to use a MySQL server with InnoDB support,
or turn off PreviewScrips by commenting out the component call in
Tickets/Update.html I’ll look into finding some more reasonable
options, though.

  • Alex

Networking – one letter away from not working

3

I have just upgraded to 3.2.0 from 3.0.9 and almost everything seems to
work fine. When I make a comment or reply to a case, i get a blank
history entry first and then the next entry with the actual comment/reply.

You are most probably using a MySQL server that doesn’t support the
InnoDB table type; the tables are falling back to MyISAM, which is
non-transactional. The “scrips preview” on Update.html tries to start a
transaction, commit a comment, and then roll it back. Without
transactions, this results in a net empty comment.
For now, the solutions are to use a MySQL server with InnoDB support,
or turn off PreviewScrips by commenting out the component call in
Tickets/Update.html I’ll look into finding some more reasonable
options, though.

If you’re using a mysql server without innodb support, That means you
have a mysql server without support for database level transactions,
which is going to hurt you pretty badly.

Jesse
4

I didn’t know MySQL does this. This being the case, I think the install
script should check whether the tables it created actually are InnoDB.
It does now; configure now fails unless your MySQL supports InnoDB. I
have also altered the README to specify that InnoDB support is needed.

  • Alex

Networking – one letter away from not working