[wp-trac] [WordPress Trac] #22853: Hyperdb redirects to wp-admin/install.php with no read servers up

WordPress Trac noreply at wordpress.org
Tue Dec 11 07:12:12 UTC 2012


#22853: Hyperdb redirects to wp-admin/install.php with no read servers up
-----------------------------+--------------------------
 Reporter:  archon810        |       Type:  defect (bug)
   Status:  new              |   Priority:  normal
Milestone:  Awaiting Review  |  Component:  Database
  Version:  3.4.2            |   Severity:  major
 Keywords:                   |
-----------------------------+--------------------------
 Hi folks. Apologies if the dev team doesn't consider
 [http://wordpress.org/extend/plugins/hyperdb/ HyperDB] core WP (I do,
 since it's used by Wordpress.com and is developed by core WP people).

 Either way, I also filed this [http://wordpress.org/support/topic/hyperdb-
 redirects-to-wp-admininstallphp-with-no-read-servers-up here], though none
 of the developers seem to be active on that support forum (hence this bug
 report to bring attention to it). If you choose to close this bug here, I
 at least appreciate if at least one of the core devs takes a look at the
 above url and comments there (matt, andy, ryan, mdawaffe, vnsavage).



 I'm enabling hyperdb on a high-traffic website but during my testing found
 pretty shocking behavior in my opinion when a certain situation occurs.

 Basically, when all db read servers are down, rather than showing the
 standard "Error establishing a database connection" page as you would
 expect, anyone visiting the site is immediately redirected to wp-
 admin/install.php. No matter if you're logged in or not, that's where you
 end up.

 I kind of understand why it happens, but I'm terrified to think that
 rather than get a descriptive DB error page, users will be instead
 directed to a page that shows up during the very first WP install.
 Moreover, I'm not sure what would happen if they got to that page and the
 read server came back up in the meantime, then they submitted the form.

 Is there a way to get hyperdb to error out when no read servers are
 available instead of having users deal with this unfriendly and
 potentially dangerous behavior?

 To test, just set all read servers to 0 in the config or just shut down
 mysql on the hosts with read > 0.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/22853>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list