SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'reason' cannot be null:

So we actually want the reason to be populated. I believe the root cause is actually an error somewhere before the write. In some of my recent work in this module I've seen this happen when there was an error returned from the Mollom API (like auth error). Can you check your logs to see if there is something like this?

Just created a Mollom free account tonight and plugged my public/private keys into this module's HEAD; it resulted in a message that "Mollom servers confirmed my keys and everything is working" or something like that. However, I do get 401 Unauthorizeds back from Mollom on the spam check requests. So, that's a thing. But, the storage shouldn't puke this hard because of an unexpected Mollom response. In cases like this, is it desired to write a record to the database? If so, should we see about making 'Reason' be something that at least vaguely hints at an error occurred in the exchange with Mollom?

Ok, I agree with @tetranz. When you don't get back a 401 (#2575951: OAuth signature computation bugs can help with that), there is indeed no "reason" given, for ham, anyway. According to the module's .install file, the reason column is supposed to store "A special reason for why a post was blocked", so we probably have correctly guessed that it is meant to store information from the mollom response, but more importantly by that description it would be expected to be valueless at least for posts that weren't blocked. And this is consistent with the responses we're seeing.

The schema gives default values for the things it asks be not null, as does the $defaults array in ResponseDataStorage::save. Reason is getting passed down to the database as null anyway because it is explicitly set null in the $data parameter passed in, but I think the schema default should be used instead in these cases. So, here's a patch that effectively overrides null values passed for non-nullable fields with the schema-specified default value for that field.

My bad, #10's patch had several issues. Here's the patch for just this issue.

I take this back - I think you are absolutely right that there are times when the reason field should be empty. However, the schema definition allows for this because there is a default value of ''. I think what is happening is that the NULL value is being explicitly set before saving rather than just being provided empty. I'm working on a fix right now. Hoping to have an updated D8 release out in the next day or so.

Hello,

I have Mollom 8.x-1.1 running on Drupal 8.1.1

I have enabled Mollom on the production site and now I am getting a WSOD when I try to create and save a node of a content type. My error log says:

Message Drupal\Core\Database\IntegrityConstraintViolationException: SQLSTATE[23000]: Integrity constraint violation: 19 NOT NULL constraint failed: node_field_data.title: INSERT INTO {node_field_data} (nid, vid, type, langcode, title, uid, status, created, changed, promote, sticky, revision_translation_affected, default_langcode, content_translation_source, content_translation_outdated) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?); Array ( [0] => 102 [1] => 102 [2] => practitioners [3] => en [4] => [5] => 1 [6] => 1 [7] => 1464655691 [8] => 1464655710 [9] => 0 [10] => 0 [11] => 1 [12] => 1 [13] => und [14] => 0 ) in Drupal\Core\Database\Connection->handleQueryException() (line 668 of /home/adaptiv9/public_html/core/lib/Drupal/Core/Database/Connection.php).

Thank you in advance for any help.

M