WordPress.org

Make WordPress Core

Opened 6 years ago

Closed 6 years ago

#5402 closed defect (bug) (invalid)

2.3.1 Registration Error

Reported by: cartpauj Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.3.1
Component: General Keywords: Registration error, MySQL, server has timed out
Focuses: Cc:

Description

I have just upgraded my blog to 2.3.1 and I now when users register on my blog they get the error below. I have tried a fresh install of 2.3.1 but still getting the error. I noticed that when I deactivate the SimpleForum Plugin the error goes away so I contacted the plugin maker and he looked at the error and the code and told me it was a WP error, which makes sense because I have his plugin running on 4 other sites without a problem. I have also tried a fresh install of his plugin but the error still exists. I'm thinking that perhaps WP 2.3.1 is just too slow and the SQL DB is timing out before the registration is completed:

ERROR

WordPress database error: [MySQL server has gone away]
SELECT meta_key, meta_value FROM wp_usermeta WHERE user_id = '1' AND meta_key = 'wp_sfadmin'

WordPress database error: [MySQL server has gone away]
SELECT meta_key, meta_value FROM wp_usermeta WHERE user_id = '1' AND meta_key = 'wp_sfadmin'

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

Change History (2)

comment:1 in reply to: ↑ description johnbillion6 years ago

  • Priority changed from highest omg bbq to normal
  • Severity changed from critical to normal

The SQL error is being triggered by SimpleForum as can be seen from the meta_key value.

Replying to cartpauj:

I noticed that when I deactivate the SimpleForum Plugin the error goes away

So what you're saying is that the registration system works fine when this plugin is not active? Then in that case it's an issue with SimpleForum and not WordPress.

comment:2 DD326 years ago

  • Milestone 2.6 deleted
  • Resolution set to invalid
  • Status changed from new to closed

Closing as Invalid; Not a WordPress issue(But infact, MySQL settings, or PHP Config relating to MySQL), See #5932 for an outdated fix.

Note: See TracTickets for help on using tickets.