I'm getting errors creating a new post in a forum. When replying to an existing post that was inserted via mailhandler, I don't have any issues. I believe the error is stemming from the fac that both the CID and TID values in the sql insert statement are null. Looking at the way the new posts are tracked, is this even right to have CID and TID values null? It seems if you have a bunch of posts with null there will be problems finding the posts later.

I guess maybe it's assuming mysql is just complaing about warnings

user warning: Incorrect integer value: '' for column 'cid' at row 1 query: INSERT INTO listhandler (msgid, nid, cid, pid, uid, mid, tid) VALUES ('
','30','','0','1','1','') in E:\websites\mog_drupal\modules\listhandler\listhandler.module on line 405.

Drupal 6.13
Access to update.php Protected
CAPTCHA Already 6 blocked form submissions
Configuration file Protected
Cron maintenance tasks Last run 1 sec ago
You can run cron manually.
Database updates Up to date
Drupal core update status Up to date
File system Writable (public download method)
GD library bundled (2.0.34 compatible)
IMAP Enabled
Mailhandler requires that PHP's IMAP extension is enabled in order to function properly.
Module and theme update status Up to date
MySQL database 5.1.36
PHP 5.2.10
PHP memory limit 512M
PHP register globals Disabled
Unicode library PHP Mbstring Extension
Update notifications Enabled
Web server Microsoft-IIS/6.0

Comments

aaronsb’s picture

Priority: Normal » Minor

Made the warnings go away by removing STRICT_TRANS_TABLES setting from mysql configuration. Perhaps add this to the documentation for installation?

philipnet’s picture

Assigned: Unassigned » philipnet
StatusFileSize
new1.05 KB

Replicated under Linux.
Patch attached.

philipnet’s picture

StatusFileSize
new1.05 KB

Better patch attached!

philipnet’s picture

Title: New post in forum results in errors » sql-mode STRICT_TRANS_TABLES results in new forum topics not being logged/emailed
Status: Active » Fixed

Committed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.