WordPress.org

1. donakarissa
   Member
   Posted 4 months ago #
   

   Receive this error in the "Header" section of the "Dashboard".

   The "*******" in the string is the first admin account for this site. (Not my admin account)

   Warning: Missing argument 2 for wpdb::prepare(), called in /home/content/c/s/l/*******/html/training/wp-content/plugins/bp-registration-options/includes/admin.php on line 19 and defined in /home/content/c/s/l/*******/html/training/wp-includes/wp-db.php on line 990

   Warning: Cannot modify header information - headers already sent by (output started at /home/content/c/s/l/*******/html/training/wp-includes/wp-db.php:990) in /home/content/c/s/l/*******/html/training/wp-includes/option.php on line 568

   Warning: Cannot modify header information - headers already sent by (output started at /home/content/c/s/l/*******/html/training/wp-includes/wp-db.php:990) in /home/content/c/s/l/*******/html/training/wp-includes/option.php on line 569

   http://wordpress.org/extend/plugins/bp-registration-options/

2. TheLastLegion
   Member
   Posted 4 months ago #
   

   Hi just wanted to say I got errors as well
   On the top of my admin pages I got this error:

   Warning: Missing argument 2 for wpdb::prepare(), called in /home/html/community/wp-content/plugins/bp-registration-options/includes/admin.php on line 19 and defined in /home/html/community/wp-includes/wp-db.php on line 990

3. Jan Dembowski
   Volunteer Mod. & Brute Squad
   Posted 4 months ago #
   

   @donakarissa Please give this a read.

   http://codex.wordpress.org/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F

   It's often your wp-config.php file that is the culprit for the headers already sent problem.

   Once you've sorted that out give this a read for that Missing argument 2 for wpdb::prepare() problem.

   http://make.wordpress.org/core/2012/12/12/php-warning-missing-argument-2-for-wpdb-prepare/

   You can make that warning go away for now by adding this to your wp-config.php file.

   @ini_set('display_errors', 0);

   If you do edit that file make sure you make a backup copy first.

   Edit: Note that that is not a fix, it just hides the warnings. The plugin author will need to update their code to really fix it.

Reply

You must log in to post.