Any update on if this will be integrated into a new release?
@johngiaconia – a function that begins with an _ is designed to be a private function used within the class. I explained how to remove the warning here:
http://wordpress.org/support/topic/wp-36-outputs-notice-warnings-escape?replies=12#post-4508678
It still needs to be fixed.
Right, is there anything specific holding up a version bump?
@ikraav – I’ve updated the development version.
I am having troubles with the define(‘SUNRISE’,’on’) when attempting to set up domain mapping. I moved sunrise.php to wp-content and tried placing define(‘SUNRISE’,’on’) on wp-config the last line and above that’s it Happy Blogging */. The define(‘SUNRISE’,’on’) is messing up the entire Network admin page. When I’ve placed the define(‘SUNRISE’,’on’) in various lines in wp-config, the Network Admin goes into a spiral and redirects the route to wp-admin.com. How do I set up domain mapping more successfully?
You are missing a semi-colon
define('SUNRISE','on')
should be
define('SUNRISE','on');
Is there any update on this? It was a month ago that this made it’s way to the dev version. Would be great to get live as my error log is filled with these messages.
@riseoflex88 – you have to manually copy the new sunrise.php into place. The built in updater will not fix this for anyone.
Download the development version and upload the sunrise.php from that zip to your wp-content directory.
Ok great, updated, I’ll monitor.
Cheers Ron.
@TCBarret – those fixes don’t work for sunrise.php. If I substitute esc_sql for escape, I get:
Fatal error: Call to undefined function esc_sql() in wp-content/sunrise.php on line 11
I’ve tried:
_escape – this works (but I understand it’s not really a fix..)
esc_sql – shows that error message
$wpdb->esc_sql – Fatal error: Call to undefined method wpdb::esc_sql() in /opt/bitnami/apps/wordpress/htdocs/wp-content/sunrise.php on line 11
I’m a WP noob, so I don’t understand why esc_sql is missing for this file but seems available for other files.
Note that replacing escape with esc_sql for all of the other plugins seemed to work, or at least I’m not seeing any errors about them. (akismet, google sitemap gen)
basically the problem is:
$dm_domain = $wpdb->escape( $_SERVER[ ‘HTTP_HOST’ ] );
the escape can be left out, as afterwards $dm_domain
is in the query in a prepared statement – meaning it’s just a waste to escape it beforehand. And it’s a $_SERVER variable anyway
$dm_domain = $_SERVER[ 'HTTP_HOST' ];
will do the trick
Is this fixed in 3.7.1 or will it be in 3.8 perhaps?