How to fix when was create social login but some database error? the errors are below

WordPress database error:

[Column 'email' cannot be null]
INSERT INTO `wp_wsluserscontacts` (`user_id`, `provider`, `identifier`, `full_name`, `email`, `profile_url`, `photo_url`) VALUES (48, 'Facebook', '000000000000', 'Vignesh', NULL, 'https://www.facebook.com/app_scoped_user_id/000000000000/', 'https://graph.facebook.com/000000000000/picture?width=150&height=150')


Warning: Cannot modify header information - headers already sent by (output started at /home/domain/public_html/wp-includes/wp-db.php:1405) in /home/domain/public_html/wp-includes/pluggable.php on line 904

Warning: Cannot modify header information - headers already sent by (output started at /home/domain/public_html/wp-includes/wp-db.php:1405) in /home/domain/public_html/wp-includes/pluggable.php on line 905

Warning: Cannot modify header information - headers already sent by (output started at /home/domain/public_html/wp-includes/wp-db.php:1405) in /home/domain/public_html/wp-includes/pluggable.php on line 906

Warning: Cannot modify header information - headers already sent by (output started at /home/domain/public_html/wp-includes/wp-db.php:1405) in /home/domain/public_html/wp-includes/pluggable.php on line 1195

Can you give us a bit more detail about what you were doing when you got this error @Vignesh_Waran. Are you using a plugin? Is it your own code?

1 Like

I use plugin name for wordpress social login

Thank you for your support

My interpretation of the problem is this:

  • An invalid INSERT is attempted.
  • the error causes output (the error message)
  • script then tries to run a header() line on the presumption the INSERT did not fail
  • because there was previous output, it causes the “headers already sent” error

I see two possible fixes. Either ensure that INSERT will not fail. Or handle a failed INSERT differently.

IMHO, the first thing you should do is to go to whatever support that plugin has available. There is a chance others have had a similar problem and you will find a solution. If not, this could be a bug that the plugin author should be made aware of in the hope it will get fixed. If that fails unfortunately that leaves two choices. Either dig into the code and fix it, or find a different plugin to replace it with.

4 Likes

Thank you for your support

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.