WordPress.org

Ready to get started?Download WordPress

Forums

WP DB Driver
[resolved] PHP Notice: Undefined property: wpdb_drivers::$real_escape (9 posts)

  1. J.D. Grimes
    Member
    Posted 1 year ago #

    Just installed this and I'm getting this repeatedly in the logs (I have WP_DEBUG on):

    PHP Notice:  Undefined property: wpdb_drivers::$real_escape in ../wp-includes/wp-db.php on line 566

    I haven't been able to track down exactly what is causing it, other than that something is calling for $wpdb->real_escape:

    function __get( $name ) {
    		if ( 'col_info' == $name )
    			$this->load_col_info();
    
    		return $this->$name; /** 566 **/
    	}

    I wasn't getting this error before installing the plugin.

    http://wordpress.org/extend/plugins/wp-db-driver/

  2. J.D. Grimes
    Member
    Posted 1 year ago #

    I think that this was in an old development version. I just updated my local SVN to the latest, and a grep for ->real_escape didn't turn up anything (before it did).

  3. Marko Heijnen
    Member
    Plugin Author

    Posted 1 year ago #

    A few days ago some changes are made to the current wpdb class. I need to apply those changes to the plugin. This will most likely take me 24 hours to do

  4. Marko Heijnen
    Member
    Plugin Author

    Posted 1 year ago #

    I just did a possible fix on the GitHub repo. Still need to test it out what can wait for a while since my laptop is broken.

  5. J.D. Grimes
    Member
    Posted 1 year ago #

    I just downloaded the plugin from GitHub, but after testing it the error is still happening. I think though that these changes have been reverted in trunk, so maybe just wait until the next RC.

  6. Marko Heijnen
    Member
    Plugin Author

    Posted 1 year ago #

    I don't think so. That variable isn't needed anymore. I did remove the one call this plugin did to the variable $real_escape. Will look into it when I can.

  7. J.D. Grimes
    Member
    Posted 1 year ago #

    I just updated to the latest nightly build of WP, and with your latest changes applied, this appears to be fixed.

  8. markmont
    Member
    Posted 12 months ago #

    This is still an issue with plugin version 1.3 when running WP 3.6-RC2 (which was released three days ago). Updating the plugin to the version in GitHub fixed the problem, without any changes to WP 3.6-RC2.

  9. Marko Heijnen
    Member
    Plugin Author

    Posted 11 months ago #

    I just dropped the new release. Sorry for the wait.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic