Hi BlueRobot,
Thanks for your response. I've set up a new installation of formtools on a test box (Apache/2.2.14, PHP 5.3.1, MySQL 5.1.44) and with the same form was able to generate the same 304 error. It definitely is data volume issue since the error is triggered when I paste a string (330 char long) into ~2/3 of the textarea fields.
I then changed the form table (and no other) from INNODB to MyISAM using this sql statement;
ALTER TABLE ft_form_1 ENGINE=MYISAM;
And it works like a charm. Pasting ~1000 char string into all textarea fields works. BlueRobot, thanks very much!
So every time I create a new form I have to remember to change the mysql engine to MyISAM.
Ben, what are the issues regarding this approach and upgrading FormTools in the future? Would it be possible to have formtools create only the form tables using the MyISAM engine by default since the form tables are created dynamically?
Cheers,
Scott
Thanks for your response. I've set up a new installation of formtools on a test box (Apache/2.2.14, PHP 5.3.1, MySQL 5.1.44) and with the same form was able to generate the same 304 error. It definitely is data volume issue since the error is triggered when I paste a string (330 char long) into ~2/3 of the textarea fields.
I then changed the form table (and no other) from INNODB to MyISAM using this sql statement;
ALTER TABLE ft_form_1 ENGINE=MYISAM;
And it works like a charm. Pasting ~1000 char string into all textarea fields works. BlueRobot, thanks very much!
So every time I create a new form I have to remember to change the mysql engine to MyISAM.
Ben, what are the issues regarding this approach and upgrading FormTools in the future? Would it be possible to have formtools create only the form tables using the MyISAM engine by default since the form tables are created dynamically?
Cheers,
Scott