WordPress.org

Ready to get started?Download WordPress

Forums

Warnings (4 posts)

  1. RebekahRuth17
    Member
    Posted 1 year ago #

    I have a warning on my site and I can't find any info on what to do about it. When I try to save or publish a new post I get the following error messages:

    Warning: Missing argument 2 for wpdb::prepare(), called in /hermes/waloraweb010/b1562/moo.rebekahruthbookscom/wp-content/plugins/digiproveblog/CopyrightProof.php on line 810 and defined in /hermes/waloraweb010/b1562/moo.rebekahruthbookscom/wp-includes/wp-db.php on line 990

    Warning: Cannot modify header information - headers already sent by (output started at /hermes/waloraweb010/b1562/moo.rebekahruthbookscom/wp-includes/wp-db.php:990) in /hermes/waloraweb010/b1562/moo.rebekahruthbookscom/wp-includes/pluggable.php on line 876

    I am not a programmer and have absolutely no idea what to do about this but it has effectively disabled my site. Help?

  2. This is coming from your "digiproveblog" plugin.

    You may want to contact the plugin developer and send them HERE.

  3. kmessinger
    Volunteer Moderator
    Posted 1 year ago #

    Error message: Warning: Missing argument 2 for wpdb::prepare(), called in ... (happens in themes and plugins)

    Fix: Your site is fine, but you may wish to turn off PHP's display errors setting. Contact your theme or plugin dev and point them to http://make.wordpress.org/core/2012/12/12/php-warning-missing-argument-2-for-wpdb-prepare/ so they can fix the underlying issue.

  4. DigiproveDevelopment
    Member
    Posted 1 year ago #

    Follow-up - If you can't get into the WordPress log-in screen as a result of this problem, the way to resolve it is to delete the directory digiproveblog, the usual location is /wp-content/plugins from your wordpress directory. This will remove all the plugin code.

    Once you do that you should be able to log in, then you can re-install the latest version (2.11) which does not have this problem.

    Once again apologies to those of you who have been affected, it was actually caused by WordPress 3.5 introducing a single more stringent warning message which in turn triggered all this stuff

    Regards
    Cian

Topic Closed

This topic has been closed to new replies.

About this Topic