Title: wordpress 3.8.1 & hyperdb
Last modified: August 21, 2016

---

# wordpress 3.8.1 & hyperdb

 *  [wpReg](https://wordpress.org/support/users/wpreg/)
 * (@wpreg)
 * [12 years, 3 months ago](https://wordpress.org/support/topic/wordpress-381-hyperdb/)
 * Can hyperdb be used with wordpress 3.8.1? If it is not compatible, are there 
   any other good alternatives to hyperdb?
 * [https://wordpress.org/plugins/hyperdb/](https://wordpress.org/plugins/hyperdb/)

Viewing 6 replies - 1 through 6 (of 6 total)

 *  [Kent Nasveschuk](https://wordpress.org/support/users/kent-nasveschuk/)
 * (@kent-nasveschuk)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/wordpress-381-hyperdb/#post-4663707)
 * I havent gotten latest hyperdb to work on 3.8.1.
 *  [Kent Nasveschuk](https://wordpress.org/support/users/kent-nasveschuk/)
 * (@kent-nasveschuk)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/wordpress-381-hyperdb/#post-4663713)
 * Update, latest hyperDB is working with WP3.8.1. The problem I had was not related
   to WP installation.
 *  Thread Starter [wpReg](https://wordpress.org/support/users/wpreg/)
 * (@wpreg)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/wordpress-381-hyperdb/#post-4663714)
 * That sounds good [@kent](https://wordpress.org/support/users/kent/) – can you
   please share some details? What did you have to do to get it to work?
 *  [Kent Nasveschuk](https://wordpress.org/support/users/kent-nasveschuk/)
 * (@kent-nasveschuk)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/wordpress-381-hyperdb/#post-4663715)
 * This is what I used to get HyperDB running with HAProxy. HAProxy listens on 6306(
   MySQL master) 3306 (MySQL slaves):
 * db-config.php
    …. $wpdb->add_database(array( ‘host’ => ‘haproxy:6306’, // If 
   port is other than 3306, use host:port. ‘user’ => ‘user’, ‘password’ => ‘password’,‘
   write’ => 1, ‘read’ => 0, ‘name’ => ‘wp_mu’, ‘dataset’ => ‘global’, ‘timeout’
   => 0.2, ));
 * $wpdb->add_database(array(
    ‘host’ => ‘haproxy:3306’, // If port is other than
   3306, use host:port. ‘user’ => ‘user’, ‘password’ => ‘password’, ‘write’ => 0,‘
   read’ => 1, ‘name’ => ‘wp_mu’, ‘dataset’ => ‘global’, ‘timeout’ => 0.2, )); ….
 * wp-config.php
    …. /* define(‘DB_NAME’, ‘wp_mu’); define(‘DB_USER’, ‘user’); define(‘
   DB_PASSWORD’, ‘password’); define(‘DB_HOST’, ‘haproxy’); */ ….
 * Thats about it.
 *  [Kent Nasveschuk](https://wordpress.org/support/users/kent-nasveschuk/)
 * (@kent-nasveschuk)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/wordpress-381-hyperdb/#post-4663716)
 * db.php goes in wp-content/
 *  Thread Starter [wpReg](https://wordpress.org/support/users/wpreg/)
 * (@wpreg)
 * [12 years, 2 months ago](https://wordpress.org/support/topic/wordpress-381-hyperdb/#post-4663756)
 * Thanks [@kent](https://wordpress.org/support/users/kent/)!!! I am able to get
   it to work as needed between master/slave MySQL servers, the next hurdle now 
   is that it doesn’t play well w3tc since they have the same file name db.php, 
   so now exploring if w3tc has the same features…
 * I found a few options where w3tc’s db.php file can be renamed, but I don’t really
   want to do that at this point…
 * thanks once again!

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘wordpress 3.8.1 & hyperdb’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/hyperdb_33353d.svg)
 * [HyperDB](https://wordpress.org/plugins/hyperdb/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/hyperdb/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/hyperdb/)
 * [Active Topics](https://wordpress.org/support/plugin/hyperdb/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/hyperdb/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/hyperdb/reviews/)

 * 6 replies
 * 2 participants
 * Last reply from: [wpReg](https://wordpress.org/support/users/wpreg/)
 * Last activity: [12 years, 2 months ago](https://wordpress.org/support/topic/wordpress-381-hyperdb/#post-4663756)
 * Status: not resolved