Updated and now has an error while creating a new email

KZeni · (This post was last modified: Nov 20th, 2009, 7:35 PM by KZeni.)

I have updated formtools to the latest version but now when I try to add/edit an email template it outputs an error after pressing "Update Email Template".

This text is shown on a white blank page (/admin/forms/edit.php?page=edit_email):

Code:
Incorrect integer value: '' for column 'email_from_account_id' at row 1

If I go back and refresh the email template list it actually seems to have added one, but everything is left blank on it.

I just noticed that when I go to the Main Settings it says I am still running Core version 2.0.0-beta-20091101 instead of the version 2.0.0-beta-20091116 that I just uploaded. Also, the Extended Client Fields says it's 1.1.1 but when I use the Check for Upgrades button it says it's still version 1.1.0.

Does anyone know the potential source of/solution for this error? I just re-uploaded formtools, but it did nothing to fix this error. Please help.

Thanks in advance.

***Ben*** · Nov 20th, 2009, 9:16 PM

Hi KZeni,

I looked over the download files & core upgrade files and everything looks okay, so it looks like it's particular to your installation. Very odd that it's not showing the correct version...

When you said you re-uploaded Form Tools, do you mean you did a fresh installation from the main download file?

- Ben

KZeni · Nov 20th, 2009, 9:39 PM

Initially it was just the upgrade files, but that didn't fix the issue so I then uploaded files from the main download file (leaving the config.php in place), but that didn't work either. That's when I posted this topic.

***Ben*** · Nov 21st, 2009, 7:44 PM

Hi KZeni,

I read your other thread in the Swift Mailer section & I'm wondering if it's something particular to your installation.

I don't suppose it would be possible for you to send me your Form Tools login info & set up some temporary FTP information so I could log on and debug the problem directly? Just email me at ben.keen@gmail.com.

Let me know! Smile

- Ben

KZeni · Nov 23rd, 2009, 10:57 AM

Email sent. Thanks.

***Ben*** · Nov 24th, 2009, 10:21 PM

Hey folks,

Just to close this thread, it turns out that the problems were caused by MySQL 5 being run in strict mode. When turning that off, the problems went away.

I've logged this as a bug, but be warned that until it's fixed, running your DB in strict mode DOES currently cause problems.

- Ben

FORUMS