SLTy Plugins

WordPress Plugins that are both practical and Spirit-Led.

 

WP Tuner 0.9.6 Comment Thread

This release: is tested on latest WP version, and generalizes support for almost any kind of unusual query.

Please post your comments and questions below. I reserve the right to snip inappropriate commentary, flame wars and so forth.

If you are reporting a problem:

  • Please set Debug Level to 1 and copy the wpTuner Diagnostics report here
  • If a specific plugin or widget is misbehaving, please note which one (if you know)

56 Responses to “WP Tuner 0.9.6 Comment Thread”

  1. ovidiu:

    hey, can you make a changelog accessible please? maybe on the plugin’s page at wordpress.org?

  2. Pete:

    Re: ovidiu (#1),
    I’ll see what’s possible. It’s all automated by WordPress… I just check changes in to their system and it automagically publishes updated releases.

  3. Leon:

    Hi, when I add the action the_content to the wptuner.php file, the content of posts and pages isn’t shown anymore (only the title and comment links are shown, the “format_text entry-content” div is empty). I added this line to wptuner.php:
    add_action(’the_content’, ‘wpTuneFilterTime’ );

    Am I doing something wrong?

  4. Pete:

    Re: Leon (#3),
    That’s a tricky one, Leon. the_content() assumes the filter will process data passed into it, and return a new version of the data. Since my filter knows nothing about the_content, it returns nothing — and that’s what you get on the page. :(

    Let me look around a bit and see if there is a general purpose way for me to set up the filter action so it automagically works with the_content and any other filters that make assumptions about what the filter does.

  5. Leon:

    Re: Pete (#4), cool, thanks! I look forward to a the next version of WP Tuner :)

  6. Redemptor:

    Please help, Pete!

    WP Tuner
    This plugin is only visible to site admins. (Update settings here; Visit MrPete at ICTA for bouquets/brickbats/help. Love it? Fill the Tip Jar.)
    Analysed in 0.005 seconds.
    wpTuner Diagnostics
    Debug level: 1
    User level: 10
    WP version: 2.8.4
    PHP version: 5.2.1
    MySQL version: 4.1.16-nt
    WP theme: Eos
    WP Tuner is not correctly configured. Please go to the Settings page using the link above, and set it up correctly. Render Time: 0.136 sec (23.2% for queries). DB queries: 20, none defective, none > 0.500 sec. Memory: 11.9MB
    Performance Analysis
    Queries triggered by plugins calling Core functions are charged to: The Plugin
    Yellow-highlighted rows indicate slow elements (more than 0.500 seconds)
    Page Generation Performance (Order: Chronological)
    (Tech note: If output buffering (OB) is not enabled at init, WP Tuner enables it so output size can be tracked.)
    Index Marker %Time %DB Time %DB Count Time DB Time DB Count Memory Output
    (msec) (msec) (kb) lev(bytes)
    0 Start 9 1 10 12.2 0.4 2 ?
    1 plugins_loaded 23 1 10 31.6 0.4 2 11,094.4 0()
    2 widgets_init 1 0 0 1.7 0.0 0 12,043.0 0()
    3 init 1 0 0 1.5 0.0 0 12,099.9 0()
    4 posts_selection 13 68 20 18.2 21.4 4 12,043.2 1(0)
    5 wp_head 11 27 20 14.4 8.4 4 12,102.0 1(1512)
    6 loop_start 16 0 0 21.9 0.0 0 12,086.4 1(2820)
    7 get_sidebar 8 0 5 10.8 0.1 1 12,093.3 1(8706)
    8 posts_selection 2 1 10 3.2 0.3 2 12,222.4 2(0)
    9 loop_start 14 -98 25 19.5 -30.9 5 12,189.3 2(143)
    10 get_footer 1 0 0 0.7 0.0 0 12,146.3 1(12985)
    11 Stop 12,158.3 1(13261)
    Total 100 0 100 135.6 0.0 20

    Plugin / Theme SQL Query Performance (Order: DB Time)
    Code Name %DB Time %DB Count DB Time DB Count
    Category (msec)
    -Core- wp-blog-header.php 37 20 11.8 4
    theme eos.1.2.7 32 10 10.0 2
    -Core- widgets 29 40 9.0 8
    -Core- wp-settings.php 1 10 0.4 2
    -Core- (Other) 0 5 0.1 1
    plugin rus-to-lat 0 5 0.1 1
    Total 90 100 31.4 18

    SQL Table Performance (Order: DB Time)
    (Tech note: The first table in a query is recorded here; complex queries may reference many tables.)
    Table %DB Time %DB Count DB Time DB Count
    (msec)
    pw_terms 57 15 17.9 3
    pw_posts 24 40 7.6 8
    pw_postmeta 16 5 5.2 1
    pw_options 1 10 0.2 2
    pw_users 1 5 0.2 1
    (N/A - Non-Table Query) 1 10 0.2 2
    pw_usermeta 0 5 0.1 1
    Total 90 100 31.4 18

    SQL Query Analysis
    20 Valid queries. None slow, none invalid. Display of normal queries is disabled.

  7. ovidiu:

    hey Pete: found a problem in conjunction with the mailpress plugin:

    `2009-09-17 08:52:40 000000 — PHP [E_NOTICE] 8 : Undefined index: class in /var/www/clients/client4/web18/web/wp-content/plugins/wptuner/wptunerdb232.php at line 86
    2009-09-17 08:52:40 000000 — PHP [E_NOTICE] 8 : Undefined index: class in /var/www/clients/client4/web18/web/wp-content/plugins/wptuner/wptunerdb232.php at line 91
    `

    http://mailpress.org - care to have a look? the above error is in the log files of mailpress…

  8. Pete:

    Re: Redemptor (#6),
    As the message says, please go to the WP Tuner admin page, and read the more detailed error message there. It should give a hint about the problem.

    Usually, it is an issue with permission for writing the configuration files…either permission on the file, or on the folder.

  9. Pete:

    Re: ovidiu (#7),
    Thanks!

    Mailpress must be turning on a more detailed level of logging. I’ll clean this up; must have missed it earlier.

    The good news: E_NOTICE messages don’t cause the program to run incorrectly. :)

  10. Daniel:

    Hi,
    WP Tuner causes conflict with DB Cache Reloaded plugin. It loads the wp-includes/wp-db.php file directly, whereas it should first try to include wp-includes/db.php file. Please use require_wp_db() function instead to include correct file (it is defined in wp-includes/functions.php file), or copy its body to your plugin.

  11. Daniel:

    One correction - plugin should try to include wp-content/db.php file first, not wp-includes/db.php.

  12. Tim Nicholson:

    Re: Pete (#4)
    Pete, thanks for writing this plugin! Although your tip on removing unused plugins was what saved me seconds off my page load times!

    the_content() only accepts and returns one parameter, which is $content. So you could just return $content at the end of your function. I believe most WP filters only accept one parameter, that parameter is just sometimes an array (like $post or $comment). Either way, you should be able to just pass it back at the end of your function.

    The format of the function is: add_action( $tag, $function_to_add, $priority, $accepted_args );

    So we can also specify that your function should be called before or after all other functions that get called to act on that $content by including a low $priority (10 is default, so anything lower than that would likely be first) or a high $priority (say, 90).

    Now on to my question about improving performance… do you have any general guidelines as to what takes so much time in the “start” section? I’ve added your function in wp-settings.php to generate separate load times for each plugin. I ended up removing one plugin as a result, but I still get long load times on the mess of stuff between the beginning of wp-settings and when the first plugin is loaded. I’m guessing there probably isn’t much that can be done to speed up that core WP startup time without hacking wp-settings to try to remove stuff that I don’t think I need to use from core WP as of right now.

    However, I know you’ve done a ton of research into this and would love to hear your opinion.

    I also found another thread about performance in the WP forums and it mostly talks about slow page loads (especially slow WP admin pages) due to hangs on various things like curl, fopen, etc. http://wordpress.org/support/topic/224410. There is a hack to shut off some of that stuff, but don’t we need it!? For pingbacks, RSS, remote posting (XML-RPC), etc!?

  13. Tim Nicholson:

    Re: Tim Nicholson (#12)
    Pate, do you have idea WHY removing unused plugins might help performance? I looked at the wp-settings.php file it reads the list of active plugins from the database. It doesn’t just loop through all the files in the plugin directory. So it really makes no sense, but it seems to work.

  14. ZDN:

    looks like WPT expects wp-config.php to be where WP sticks it by default. maybe WPT could/should use the same method as WP for locating the config (which can be up a directory (or 2?)). ex: if WP is installed in root, then /home/user/www/wp-config.php is default, but i keep mine in home/user/wp-config.php for xtra security and would rather not have to move it to run WPT.
    flowers and beer and peace

  15. Pete:

    Re: Tim Nicholson (#13),
    The list of active plugins IS read from the DB, but there are some loops that look at all plugins. I’ve not taken time to analyze it completely. (If you are interested and have time, the easy way in Windows is: install System Internals’ FileMon, then run Wordpress on your local computer. You’ll soon see the issue.)

    The main reasons for slow startup seem to be:
    - too many plugins
    - badly written plugins
    - inefficient/wasteful DB access
    - cross-site access

    That last one IS needed sometimes, but certainly ought to be cached. I recently saw a system that did 20 accesses to eBay on every page load. At busy times of day it took 3 minutes to load the page! Pretty sick.

  16. Pete:

    Re: Daniel (#11),
    Thanks, Daniel. I’ll look into that before the next release.

    That’s some of the trickiest code in the system. wpTuner has to preempt the loading of database code, in order to properly instrument DB access. To be compatible with another DB plugin, I’m going to have to test that pretty carefully!

  17. Pete:

    Re: ZDN (#14),
    Sorry about that. Support for up-level wp-content is (relatively) recent. I’ll see what I can do to fix that in the next release. AND, I’ll try to move the wpTuner startup code earlier in the load cycle. Might as well have it in index.php for that matter :)

  18. Pete:

    Folks, I want you to know I have not forgotten wpTuner.

    Unfortunately, I’ve got to spend most of my time on other things right now (financial and other priorities), but I’ll get back to this.

  19. Daniel:

    Re: Pete (#16),
    I have just released DB Cache Reloaded 2.0 - it introduces Wrapper Mode. In this mode my plugin can work with WP Tuner at the same time. There is one problem only - WP Tuner incorrectly shows who executes query. I have posted a small fix for this on WP Forum.

  20. Vladimir:

    Hi Pete

    I just tested your plugin on one of my site and it work great but some results are bit puzzling. Analysis states that slowest is start and almost 80% of loading time. Is it then a hosting problem? Another one is get_footer (around 10% of loading time). Any thought on that?
    Thnx

  21. jeremyclarke:

    Hey Pete,

    I love WP-Tuner, I mention it all the time when I to WordCamp talks, it blows everyone’s minds.

    I know the CSS isn’t that important because its only admins that see it, but I think WPTuner could be styled in a way that made it feel cleaner and be easier to read through. I worked out a style that is similar to yours but with tweaked contrast and spacing for the tables. I hope you consider integrating it into WPTuner, I think a lot of people would appreciate it.

    Here’s how it looks in the admin:
    http://simianuprising.com/wp-content/uploads/2009/12/wptuner-cssmod-admin.png

    Here’s how it looks with kubrick:
    http://simianuprising.com/wp-content/uploads/2009/12/wptuner-cssmod-kubrick.png

    I made a svn .diff of the changes to the css in wptunershow.php, you can find it here:
    http://pastie.org/748351

    And here is a paste of the entire wptunershow.php file with my css modifications:
    http://pastie.org/748355

    Thanks for your work on the plugin!

  22. Steve Axworthy:

    Hello,

    I am trying to see why my WPMU installation is slow and have installed the WP Tuner Plugin… I have many lines showing as slow and would like to learn what this means… should I paste the results here or is there another way to have others review it? Which preset should I use if I am going to paste the results here?

    Thanks!
    Steve

  23. Mike_Lakritz:

    after activating plugin, get only blank pages on frontend. here is report after setting debugging to 1. (i know, sucks we’re running php 4 etc, but we’re trying to find perfomance issues we are having before moving to our php5+/mysql5+ box.)

    WP Tuner
    This plugin is only visible to site admins. (Update settings here; Visit MrPete at ICTA for bouquets/brickbats/help. Love it? Fill the Tip Jar.)
    Analysed in 0.010 seconds.
    wpTuner Diagnostics
    Debug level: 1
    User level: 10
    WP version: 2.9.1
    PHP version: 4.3.9
    MySQL version: 4.1.12
    WP theme: WordPress Default/regenexx
    Render Time: 0.641 cpu sec (98% load, 0.035 startup). Clock: 0.652 sec (2.9% for queries). DB queries: 19, none defective, none > 0.500 sec. Memory: 16.0MB
    Performance Analysis
    Queries triggered by plugins calling Core functions are charged to: The Plugin
    Yellow-highlighted rows indicate slow elements (more than 0.500 seconds)
    Page Generation Performance (Order: Chronological)
    (Tech note: If output buffering (OB) is not enabled at init, WP Tuner enables it so output size can be tracked.)
    Index Marker %Time %DB Time %DB Count Time DB Time DB Count Memory Output
    (msec) (msec) (kb) lev(bytes)
    0 Start 71 59 16 460.3 11.3 3 ?
    1 plugins_loaded 3 7 11 20.7 1.3 2 13,311.7 0()
    2 widgets_init 2 0 0 11.1 0.0 0 13,595.9 0()
    3 init 16 7 11 105.0 1.3 2 13,685.1 0()
    4 admin_init 2 3 5 12.1 0.5 1 16,279.4 1(0)
    5 admin_head 4 0 0 23.0 0.0 0 16,321.0 1(2873)
    6 admin_notices 3 25 58 19.7 4.7 11 16,395.2 1(14280)
    7 admin_footer 0 0 0 0.2 0.0 0 16,398.1 1(22323)
    8 Stop 16,398.2 1(22462)
    Total 100 100 100 652.0 19.1 19

    Plugin / Theme SQL Query Performance (Order: DB Time)
    Code Name %DB Time %DB Count DB Time DB Count
    Category (msec)
    -Core- (Other) 58 11 11.1 2
    plugin wptuner 22 53 4.2 10
    -Core- wp-admin 9 16 1.8 3
    -Core- wp-settings.php 7 11 1.3 2
    plugin contactforms 3 5 0.5 1
    -Core- (DB Constructor/Startup) 1 5 0.2 1
    Total 100 100 19.1 19

    SQL Table Performance (Order: DB Time)
    (Tech note: The first table in a query is recorded here; complex queries may reference many tables.)
    Table %DB Time %DB Count DB Time DB Count
    (msec)
    wp_options 80 63 15.3 12
    wp_usermeta 9 16 1.8 3
    (N/A - Non-Table Query) 4 11 0.8 2
    wp_comments 4 5 0.8 1
    wp_users 3 5 0.5 1
    Total 100 100 19.1 19

    SQL Query Analysis
    19 Valid queries. None slow, none invalid. Display of normal queries is disabled.

  24. Alex W:

    Hi Pete,

    Just found your plugin today while troubleshooting. I’m going to paste my output below, but I’m more curious to know: I have a slow “init”, how can i figure out why and fix it? I know it’s sort of a general question, but I figured you’d be the guy to ask :-)

    Currently, my init is taking two minutes. That’s right, 120 seconds per page load. Needless to say, it’s painful. Here’s the kicker though–it’s only doing this on ONE of my WPMU sites! I’ve already disabled plugins and changed the theme, but to no avail.

    Here’s the WPTuner output:
    Index Marker %Time %DB Time %DB Count Time DB Time DB Count Memory Output
    (msec) (msec) (kb) lev(bytes)
    0 Start 0 2 8 373.6 0.7 7 ?
    1 plugins_loaded 1 2 5 1,098.5 1.0 5 11,387.6 0()
    2 widgets_init 0 1 1 2.4 0.3 1 14,388.7 0()
    3 init 99 62 57 120,268.5 27.1 52 14,418.3 0()
    4 admin_init 0 2 8 37.5 0.7 7 19,124.7 1(0)
    5 admin_head 0 1 4 15.0 0.5 4 19,552.2 1(2438)
    6 admin_notices 0 31 16 50.0 13.4 15 19,612.6 1(17649)
    7 admin_footer 0 0 0 0.1 0.0 0 19,585.0 1(58190)
    8 Stop 19,585.2 1(58190)
    Total 100 100 100 121,845.6 43.7 91

    So… any ideas?
    Best,
    Alex

  25. Ric J:

    Hi there, I have filled my code with multiple wpTuneMarkTime statements but nothing appears in the log. How is that?
    WP 2.9.2

  26. Zafrir:

    Just installed, LOOKS GREAT!
    I see a yellow line on the first line “Start” takes 70% of the time - how cal I debug/find the cause?
    thanks,

  27. Richard:

    I have a a LOOOONG Load time. WP Tuner reports that widgets-init is taking 90%+ of of this. I would also like to know where /how to troubleshoot.
    I have removed all unused plugins, and check code on all widgets….. but No change I’m afraid.

  28. Pete:

    Re: Daniel (#19),
    I’m looking at your patch, Daniel, and will also examine your plugin. I will try to make mine compatible with yours if possible, and if it makes sense.

    I have some skepticism about this. To me, your plugin sounds not as helpful as advertised, at least on the surface. Normally, MySQL is already very efficient about caching database queries, and does so at a low level. So adding a cache on top is not going to speed things up but rather slow it down. If DB Cache actually increases speed, it ought to indicate either a coding problem in one of the plugins you use, or a need to properly tune the MySQL parameters on the server (use phpMyAdmin to do that!).

    Meanwhile, the HTML caches really do increase performance on real, heavily loaded, blogs. A well tuned blog spends most of its CPU time generating HTML… so avoiding that time can speed things up considerably.

    BUT… that’s all just theory :) I’ll take a look in the weeks ahead and see what comes of it!

  29. Pete:

    Re: jeremyclarke (#21),
    Jeremy, thanks! I’ll work what you’ve done into my next release.

  30. Pete:

    Re: Vladimir (#20),
    The pattern you describe could be a variety of things. You’d have to add more diagnostic wpTuner calls to the code to see, such as the FAQ example about tracking plugin load times:
    http://wordpress.org/extend/plugins/wptuner/other_notes/

    As a guess, it sounds like a plugin is doing something slow :)

  31. Pete:

    Re: Steve Axworthy (#22),
    Hi Steve,

    Sorry but at this time we don’t have a community of volunteers available to analyze performance of your system for you. This is pretty much a do-it-yourself thing!

  32. Pete:

    Re: Mike_Lakritz (#23),
    Hi Mike… sorry for the slow reply. If you ever see this…

    1) Did you fix it?
    2) Your question is confusing. You say you only get blank pages, yet you were able to copy and paste the output of wpTuner, which comes from the bottom of the page. How is that?

    Once I understand your situation better, I can try to replicate it. I suspect it was a theme issue…

  33. Pete:

    Re: Alex W (#24),
    WOW. That’s horrible!

    My past experience says there’s still something strange injected into your system flow… and most likely it is a (set of) access to an external website.

    As described elsewhere, I once saw a plugin that caused s blog site to do 20 accesses to eBay.com during startup… and on a busy day this would slow the site down just the way you are seeing.

    How to discover the problem? See the advanced use FAQ here…
    http://wordpress.org/extend/plugins/wptuner/other_notes/
    …and insert wpTuneMarkTime(’xyz’) calls throughout the WP code executed during the ‘init’ phase.

    Yeah… pretty advanced stuff.

    Tell us what you find once the puzzle is solved!

    (I’d offer consulting help to find it but am booked through most of the summer.)

  34. Pete:

    Re: Ric J (#25),
    Are you seeing any other output from wpTuner?
    If not, you’ve got another kind of issue.
    If so, then either that code is not executing, or you have not inserted it correctly into the WP code base.

    wpTuneMarkTime() is how wpTuner itself logs things. :)

  35. Pete:

    Re: Zafrir (#26),
    Did you turn on all of WP Tuner’s capabilities? It could be any of several things, such as a slow DB access in a plugin.

    You might need to diagnose your plugins, using the code changes described in
    http://wordpress.org/extend/plugins/wptuner/other_notes/

  36. Pete:

    Re: Richard (#27),
    AFAIK, you can do something to diagnose widget init times in a way similar to plugin inits, as described here:
    http://wordpress.org/extend/plugins/wptuner/other_notes/

    Please tell us what you find!

    Thanks…

  37. Pete:

    NOTE

    I’m about to start working on the next release of WP Tuner. Any further ideas and feedback much appreciated!

  38. rxs:

    WP Tuner is broken on wp3.0 wo logs. Next release will be in time. Thanks for plugin.

  39. rxs:

    I fix broken WP Tuner on wp3.0 by renaming folder wptuner (through ftp) to another name.
    why is it works ?

  40. downloader:

    I keep listening to the news speak about getting free online grant applications so I have been looking around for the best site to get one.

  41. [...] Кстати, тред обсуждения плагина WP Tuner [...]

  42. Matt Herzberger:

    When I install and activate this plugin my site crashes. The site goes blank white and I can’t get on front end or backend. I suspect its a plugin computability issue. Have you heard of this before?

  43. [...] WP Tuner 0.9.6 Comment Thread « SLTy Plugins 9 loop_start 14 -98 25 19.5 -30.9 5 12189.3 2(143).. For pingbacks, RSS, remote posting (XML-RPC), etc!.. k..i agree with you…but can you give us more details about this subject?…thanks :). after activating plugin, get only blank pages on frontend. here is report after setting debugging to 1..blogs.icta.net/plugins/2009/08/24/wptuner-096-comments/ - WP Tuner 0.9.6 Comment Thread « SLTy Plugins [...]

  44. Marco Gonzalez:

    I had the same problem as Matt, upon activating the plugin all I got was the Blank Screen of Death. I fixed it by retrieving the wp-config.php file via FTP, deleting the WP-Tuner section manually and then re-uploading.

  45. Shawn:

    Same here. Activating the plugin produced white screen. Removing lines from config fixed the problem long enough for me to deactivate the plugin.

  46. Ovidiu:

    hey Mrpete, I’m in need of your plugin’s help again but I can’t get it configured again. as soon as I activate the wp-config.php lines everything stops working. here is the desired diag report:

    I also see that on its wordpress plugin page there are a couple of reports of it being incompatible with w3 total cache.

    WP Tuner
    This plugin is only visible to site admins. (Update settings here; Visit MrPete at ICTA for bouquets/brickbats/help. Love it? Fill the Tip Jar.)
    Analysed in 0.920 seconds.
    wpTuner Diagnostics
    Debug level: 1
    User level: 10
    WP version: 3.0.1
    PHP version: 5.2.6-1+lenny9
    MySQL version: 5.0.51a-24+lenny4-log
    WP theme: Leviathan

  47. Alex:

    Hi,

    I installed and activated your plugin and now my site is not accessible (only blank pages).

    How can I un-install the plugin and make everything go back to normal?

  48. David:

    Hi, Mr. Pete and all you folks trying to get wptuner to run on WP3.0
    by doing a little sleuthing, we were able to get wptuner to run in WP3.0
    see the instructions here:

    http://wordpress.org/support/topic/plugin-wp-tuner-wp-tuner-die?replies=10
    (read all the way to the bottom)

    It was an easy fix, and Mr. Pete, I’d like to ask that you update the plugin and re-commit it to the WP SVN so that the rest of the world can use your great plugin without having to endure the “Holy Mackeral, my site just died and I can’t even bring it up to disable the wptuner plugin!!!” moment.

    By the way, Mr. Pete, I have some feature requests if you are interested in taking this up again! Thanks for the plugin. Most helpful.

  49. Andreas:

    Your plugin just save my life . Please accept my honest thanks. :D im just too happy to let you know. Donation 1X494007GM093672X.

  50. Ovidiu:

    just checking whether you found some time to fix the plugin yet? we need it ;-)

  51. Vios:

    Warning: mysql_get_server_info() expects parameter 1 to be resource, null given in T:\home\Vioblog\www\wp-includes\wp-db.php on line 1550

    Warning: Cannot modify header information - headers already sent by (output started at T:\home\Vioblog\www\wp-includes\wp-db.php:1550) in T:\home\Vioblog\www\wp-admin\install.php on line 54

  52. Ric:

    Hi.

    Installed WPTuner on an updated WP site, running PHP 5 and MySQL 5.0, and now I get this message when I try to activate it:

    Insufficient Requirements

    You cannot install because WordPress 3.2.1 requires MySQL version 5.0 or higher. You are running version .

    I can’t seem to get into my admin any more.

  53. reshuffle:

    I installed your plugin hoping to find the problem in another plugin, but after I activate wp tuner I get this message when I access any page on the site:

    Insufficient Requirements
    You cannot install because WordPress 3.3 requires MySQL version 5.0 or higher. You are running version .

    I am running MYSQL 5.1. I did have write access on the wpconfig file so that your program could add what it needed to. I removed the code that it added and write access so that it doesn’t try to add the code again, and the error went away. But I’m sure it’s not working correctly. Can you help me?

  54. septemous:

    Hi - I’m getting the same issue as Ric above ??

    thoughts?

  55. Ovidiu:

    Hey Mr. Pete, any chance you’l keep this plugin updated or is it time to say goodbye? ;-)

  56. pankaj:

    I hv issue as soon as i activated WPtuner on my site

    My site is hosted on godaddy and its way slow from last few days even though we have not added any pages or anything http://www.helpmecure.in and today when we tried installing the WPtuner plugin to check what is the issue as i click on Activate Plugin it goes to install.php …and now mess is url of the site and admin url goes to http://www.helpmecure.in/wp-admin/install.php

    Can some one help us out to rectify the same …if we remove the plugin manually will help ??? please advice

Leave a Reply

Quicktags:

Pages

Blogs

Quick Tip Jar

Currency:

Amount:

Categories

Tags

Recent Posts

Recent Comments

WP Tuner 0.9.4 comment thread

About

WP Tuner 0.9.6 Comment Thread

WP Tuner Plugin

Meta

Other Notes