WordPress.org

Support

Support » Plugins and Hacks » [Plugin: WP Tuner] wp tuner, die()

[Plugin: WP Tuner] wp tuner, die()

  • 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.

Viewing 15 replies - 1 through 15 (of 22 total)
  • rsknowles

    @rsknowles

    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.

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

    Moderator Sergey Biryukov

    @sergeybiryukov

    WordPress Dev

    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:
      <?php
      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
      else
      	@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.

    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!. 🙂

    Moderator Sergey Biryukov

    @sergeybiryukov

    WordPress Dev

    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.

    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.

    Guys, RENAME FOLDER WPTUNER TO WPTUNER1 !!!!!
    And plugin wll work!!!

    Moderator Sergey Biryukov

    @sergeybiryukov

    WordPress Dev

    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.

    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!

    Moderator Sergey Biryukov

    @sergeybiryukov

    WordPress Dev

    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.

    I got it to work, also. Thanks!

    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------------------

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

    Moderator Sergey Biryukov

    @sergeybiryukov

    WordPress Dev

    Why does the plugin claim to be 3.1 compatible

    It doesn’t:

    Compatible up to: 2.8.4

    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.

Viewing 15 replies - 1 through 15 (of 22 total)
  • The topic ‘[Plugin: WP Tuner] wp tuner, die()’ is closed to new replies.