Support » Plugin: Inbound Brew » PHP Fatal error: Uncaught Illuminate\\Database\\QueryException

  • Resolved sollers

    (@sollers)


    Running this on PHP7, latest wp version…

    [Wed Nov 23 04:41:41.049613 2016] [:error] [pid 2077] [client 172.xx.xx.xxx:12148] PHP Fatal error: Uncaught Illuminate\\Database\\QueryException: SQLSTATE[HY000]: General error: 1364 Field 'social_name_facebook' doesn't have a default value (SQL: insert into 'wp_2_ib_settings' ('updated_at', 'created_at') values (2016-11-23 04:41:41, 2016-11-23 04:41:41)) in /home/user123/website1/wp-content/plugins/inbound-brew/vendor/illuminate/database/Illuminate/Database/Connection.php:555\nStack trace:\n#0 /home/user123/website1/wp-content/plugins/inbound-brew/vendor/illuminate/database/Illuminate/Database/Connection.php(338): Illuminate\\Database\\Connection->run('insert into 'wp...', Array, Object(Closure))\n#1 /home/user123/website1/wp-content/plugins/inbound-brew/vendor/illuminate/database/Illuminate/Database/Connection.php(295): Illuminate\\Database\\Connection->statement('insert into 'wp...', Array)\n#2 /home/user123/website1/wp-content/plugins/inbound-brew/vendor/illuminate/database/Illuminate/Database/Query/Processors/Processor.php(30): Illuminate\\Database\\Connection->insert('insert into 'wp...', Array)\n#3 /home/acc in /home/user123/website1/wp-content/plugins/inbound-brew/vendor/illuminate/database/Illuminate/Database/Connection.php on line 555, referer: http://www.site.com/wp-admin/edit.php?post_type=wp-lead

    • This topic was modified 3 years, 2 months ago by .
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Chris Fontes

    (@chrisfontes)

    Thank you so much for bringing this to our attention. We will work on this immediately and update you here when there is a patch (should be today).

    Plugin Author Chris Fontes

    (@chrisfontes)

    Okay, so there appears to be a new setting in MySQL 5.7.5 called STRICT_TRANS_TABLES. When this is set, MySQL is VERY picky about certain things such as inserts when there is no default value – this would normally throw a warning, but with STRICT_TRANS_TABLES enabled, it throws a fatal error.

    I suggest disabling STRICT_TRANS_TABLES for the time being while we work on making sure all fields have defaults.

    There is a good chance that a LOT of software will run into this same issue, as it is not always common to set a default for every field (though, arguably, it SHOULD be common).

    I will let you know when we update this, but it is quite the overhaul, so it will take some time.

    Plugin Author Chris Fontes

    (@chrisfontes)

    @sollers We have resolved the issue. The strict setting wasn’t new to MySQL 5.7, but defaulted on instead of off like in previous version (just to correct my above comment).

    We are pushing out version 1.6.0 of the plugin I write this, which includes the fix to function even if strict mode is enabled. Please let us know if you have any more issues, questions, or feedback.

    Thanks!
    Chris

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘PHP Fatal error: Uncaught Illuminate\\Database\\QueryException’ is closed to new replies.