Is this plugin no longer supported?

  • WordPress is the most powerful content management system in the world and it is really needed to host more sites in a multisite network without any problems. It is really difficult to stick to a single database in a multisite. It is necessary to easily partition subsites into different databases.

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

  • It is really a shame that this plugin seems to have been abandoned. There appear to be major compatibility issues with more current version of MySQL. With HyperDB active using newer MySQL versions it is not possible to properly run through the initial WordPress install without errors about column default values. If you initialize a site without HyperDB active then you can get past this issue but then you run into errors with being able to create new posts.

    It also seems related that with HyperDB active that WordPress is not able to properly detect some aspects of the database specifically I can see in the Health Check that “Database collation” is blank, whereas with HyperDB deactivated this is properly populated. “Database collation” is an aspect that is not consistent and compatible between MySQL & MariaDB versions.

    It actually appears that HyperDB is really only compatible with MySQL 5.6.

    To follow up with either MySQl 5.7 or MySQL 8.0 with HyperDB active the following is an example of the sort of error when trying to install a site the very first time.

    WordPress database error: [Invalid default value for 'user_registered']
    CREATE TABLE wp_users ( ID bigint(20) unsigned NOT NULL auto_increment, user_login varchar(60) NOT NULL default '', user_pass varchar(255) NOT NULL default '', user_nicename varchar(50) NOT NULL default '', user_email varchar(100) NOT NULL default '', user_url varchar(100) NOT NULL default '', user_registered datetime NOT NULL default '0000-00-00 00:00:00', user_activation_key varchar(255) NOT NULL default '', user_status int(11) NOT NULL default '0', display_name varchar(250) NOT NULL default '', PRIMARY KEY (ID), KEY user_login_key (user_login), KEY user_nicename (user_nicename), KEY user_email (user_email) ) DEFAULT CHARACTER SET utf8

    Without HyperDB active this error doesn’t occur. After reactivating HyperDB then there are issues with creating new posts with the following sort of error:

    Fatal error: Uncaught Error: Attempt to assign property "post_content" on null in /var/www/html/web/wp/wp-admin/includes/post.php:808 Stack trace: #0 /var/www/html/web/wp/wp-admin/post-new.php(66): get_default_post_to_edit('page', true) #1 {main} thrown in /var/www/html/web/wp/wp-admin/includes/post.php on line 808

    From everything we’ve seen this doesn’t occur with MariaDB versions or AWS Aurora DB versions.

    Thread Starter thecreator01

    (@thecreator01)

    I guess there is no other load balancing or database fragmentation plugin for WordPress multisite. Or an alternative solution for this? @tnolte

    I’ve used HyperDB in the past (a few years ago) but moved to using ProxySQL instead. In terms of a replacement plugin, ludicrousdb appears to be a fork of HyperDB which is still being updated & supported: https://github.com/stuttter/ludicrousdb

    Thread Starter thecreator01

    (@thecreator01)

    Hello, this looks great. I will definitely look into it and thank you for your message. @daveyp

    WordPress definitely needs a plugin like this and it should always be supported.

    I can’t even enable this plugin

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.