WP Tuner
wp tuner, die() (23 posts)

  1. jensg
    Posted 4 years ago #

    If I enable wp tuner, it simply dies, i can't even go into my admin panel anymore. I had to rename/delete the directory wptuner to regain access to my blog.

  2. rsknowles
    Posted 4 years ago #

    I may have a similar problem. I activate the plugin and I get a blank white screen. I fixed the issue by removing wp tuner entries from wp-config.php and disabling the plugin. Sad... I had high hopes for this plugin.

  3. Li-An
    Posted 4 years ago #

    Same think. Completely incompatible with WP 3.0. Too bad.

  4. Sergey Biryukov
    WordPress Dev
    Posted 4 years ago #

    I seem to have found a workaround for WP Tuner 0.9.6 on WordPress 3.0.x.

    1. Create wp-content/db.php file with this code:
      global $wpTunerStart, $wpTunerStartCPU;
      $wpTunerStart = microtime(); // get start time as early as we can
      if ( function_exists( 'getrusage' ) ) { $wpTunerStartCPU = getrusage(); }
      if ( file_exists(dirname(__FILE__).'/plugins/wptuner/wptunertop.php') )
      	@include_once(dirname(__FILE__).'/plugins/wptuner/wptunertop.php'); // fire up WPTuner
      	@include_once(ABSPATH . WPINC . '/wp-db.php');

      Note the global variables and slightly different path if copying the code from wp-config.php.

    2. Remove the plugin's code from wp-config.php.
    3. Open wptunertop.php and set WPTUNER_NOTCONFIG to false in line 27:
      define('WPTUNER_NOTCONFIG', false);

    The purpose of wptunertop.php is to load the plugin as early as possible, before the inclusion of wp-db.php, which is then included by the plugin itself. This approach is not compatible with WordPress 3.0, because wpdb constructor calls is_multisite(), which is not defined yet due to the wrong calling sequence.

    Being called from wp-content/db.php, the file is still loaded before database initialization, so the plugin works as intended.

  5. Gracklor
    Posted 4 years ago #

    I will try your work-around later (when I'm not doing homework). It seemed to work, but then WPTuner Broker WordPress again. Too bad. Looked like a powerful app when I saw it for a few minutes!. :-)

  6. Sergey Biryukov
    WordPress Dev
    Posted 4 years ago #

    I've been using this trick for a couple of months and it still works so far :-)
    The only issue I can think of is when you deactivate and reactivate the plugin, it changes wp-config.php again. In this case you need to repeat step 2. If you describe the exact problem, perhaps a solution can be found.

  7. rylar22
    Posted 4 years ago #

    I gave this a try and still have the white screen of death on the admin screen.

    I also noticed when opening this plugin to preform this edit that the plugin author is in violation of the GPL. The plugin shouldn't have been accepted by WordPress.org:

    Copyright 2008 ICTA / Mr Pete (email : WP-Tuner at ICTA dot net)

    I have not yet chosen a license for this software.

    For now, if you have received specific written permission from me
    to use this software, then you are free to use it personally according
    to the terms I gave you. You may not redistribute it to others.

  8. Den999
    Posted 4 years ago #

    And plugin wll work!!!

  9. Sergey Biryukov
    WordPress Dev
    Posted 4 years ago #

    Renaming the plugin folder just allows you to access the admin area again if it has been broken. The only way I know so far to make the plugin actually work is to perform the steps described above.

  10. dwertheimer
    Posted 4 years ago #

    The tip above works great. The problem is that every time the plugin does anything, it tries to re-write wp-config.php, which will give you white screen of death again and again.

    Simple fix:

    open wptuner/wptunersetup.php

    comment out the TWO calls to to the wpconfig injector, e.g.

    // wptuner_wpconfig_inject();

    (don't comment out the function declaration itself or you'll have issues)

    then you should go good to go!

  11. Sergey Biryukov
    WordPress Dev
    Posted 4 years ago #

    dwertheimer, thanks for pointing this out. On my install the plugin was updating wp-config.php on activation. For some reason I didn't think of a solution for this.

  12. Gracklor
    Posted 4 years ago #

    I got it to work, also. Thanks!

  13. dwertheimer
    Posted 4 years ago #

    Glad that worked for you guys too.

    For everyone else, MAKE SURE YOU IMPLEMENT THOSE CHANGES to the plugin code BEFORE YOU ACTIVATE IT. If you see the white screen of death, it just means the injector got to your site config before you made the changes.

    If that's the case, it's no big deal, just open your wp-config.php file in the filesystem scroll to the bottom, and remove the code that was injected by the plugin:

    //WP Tuner Plugin by MrPete------------
    //-END WP Tuner Plugin------------------
  14. nstoker
    Posted 4 years ago #

    Why does the plugin claim to be 3.1 compatible if it's not??? I'll wait for a version that's been fixed...

  15. Sergey Biryukov
    WordPress Dev
    Posted 4 years ago #

    Why does the plugin claim to be 3.1 compatible

    It doesn't:

    Compatible up to: 2.8.4

  16. nstoker
    Posted 4 years ago #

    Yes - my mistake - I got confused between the plugin description, which says 2.8.4, and the layout in the plugin directory page http://wordpress.org/extend/plugins/wptuner/, where the dropdown menu after 'compatibility' makes it look (to me) like it is saying the plugin is 3.1 compatible. Apologies.

  17. MrPeteH
    Plugin Author

    Posted 4 years ago #

    My deepest apologies to everyone! I have not been paying attention to developments as I ought (due to Real Life challenges).

    I will squeeze out some time to bring this fully up to date ASAP.

  18. Galerio
    Posted 4 years ago #

    Create wp-content/db.php file with this code:

    It doesn't function for me. I have Wp 3.1.2.

    I have created the file db.php in wp-content with the code, but then my wordpress shows the page of the initial installation of WordPress!!

    What's wrong?

  19. Sergey Biryukov
    WordPress Dev
    Posted 4 years ago #

    That only worked in WP 3.0.x. I haven't yet found a worthy solution for 3.1.x.

  20. Ovidiu
    Posted 4 years ago #

    @MrPete: we need you here :-)

  21. WPsites
    Posted 4 years ago #

    I think I have found a solution:

    In wptunertop.php find the below line and comment it out.
    $wpdb = new wpdb_wptunerversion(DB_USER, DB_PASSWORD, DB_NAME, DB_HOST);

    Seems to work.

  22. Ovidiu
    Posted 3 years ago #


    your change is in addition to others suggested here or works on its own?

  23. WPsites
    Posted 3 years ago #

    That on it's own worked on a recent version of WP

Topic Closed

This topic has been closed to new replies.

About this Plugin

  • WP Tuner
  • Frequently Asked Questions
  • Support Threads
  • Reviews

About this Topic