SLTy Plugins

WordPress Plugins that are both practical and Spirit-Led.

 

WP Tuner rev 0.9.1: User Hints & Questions

This is the archive of WP Tuner 0.9.1 user comments.

21 Responses to “WP Tuner rev 0.9.1: User Hints & Questions”

  1. Alexander - StrategieVincenti:

    Hi Pete,

    your plugin reported following Bug:

    wpTuner Report
    Please report, wpTuner could not match this complex (or possibly invalid) database query:

    DESC wp_comments

    wptunershow->Parse_Query() wp-content/plugins/wptuner/wptunershow.php 276

    What does it mean ?
    What do I have to do to fix this ?

    Thanks in advance

    ciao
    alexander

  2. Mr Pete:

    Re: Alexander - StrategieVincenti (#1),
    WP Tuner is reporting a query that it could not understand.

    If you enable full query reporting (easiest is the “Show Everything” preset), you should find that string (DESC wp_comments) somewhere in the list. Along with the string, you will also see a filename and line number where the query was generated.

    Please do tell me what you learn!

    Also, please set the WP Tuner Debug Level to 31, and copy the resulting report here. It should include a complete list of your installed plugins. (You can set DebugLevel back to zero when you are done.)

    This query is not part of WordPress; it is likely in one of your plugins, widgets or your theme. I am very curious about this, as we’ve had one other similar report… but nobody has given any more info about the source of the problem!

    Once we know where the query comes from, I can probably help you decide how to fix the problem (I do not yet want to assume the problem is in your system; it could be something very minor for all I know.)

  3. Alexander - StrategieVincenti:

    Hi Mr Pete,

    thank you for your answer.
    I get in the SQL Query Analysis following result:

    DESC wp_comments
    [wp-content/plugins/subscribe-to-comments/subscribe-to-comments.php(259)->db_upgrade_check()]

    and the Query time for this item is 7.733 msec, the longest of the 10 items listed (a couple took 0.6 and all the other were under 0.5 msecs).
    Deactivating the “Subscribe to comments plugin” by Mark Jaquith solves the bug and your plugin doesn’t report any more bugs. Although that plugin is really one I want to keep (I don’t understand why Automattic doesn’t provide the subscription to comments as a built in feature of Wordpress), so what could I do to fix the problem ?

    Thanks in advance

    ciao
    alex

  4. Viktor:

    Hi Mr Pete.
    Here report of your plugin:
    —————————————————————————————-
    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.001 seconds.
    wpTuner Diagnostics
    Debug level: 1
    User level: 10
    WP version: 2.3.3
    PHP version: 5.2.6
    MySQL version: 4.1.22-standard
    WP theme: Blue3
    WP Tuner is not correctly configured. Please go to the Settings page using the link above, and set it up correctly. Render Time: 1227247193.494 sec (0.0% for queries). DB queries: 28, None defective, none slower than 0.500 seconds. Memory: 7.8MB
    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 100 0 25 1,227,247,193,388.2 0.0 7 ?
    1 N/A: old WP rev 0 0 11 59.9 0.0 3 5,750.4 0()
    2 N/A: old WP rev 0 0 0 2.1 0.0 0 6,971.1 0()
    3 N/A: old WP rev 0 0 25 33.4 0.0 7 6,998.8 0()
    4 N/A: old WP rev 0 0 0 2.2 0.0 0 7,967.5 1(3109)
    5 N/A: old WP rev 0 0 39 8.2 0.0 11 7,991.5 1(4849)
    6 N/A: old WP rev 0 0 0 0.1 0.0 0 8,017.0 1(12769)
    7 Stop 8,017.0 1(12769)
    Total 100 0 100 1,227,247,193,494.0 0.0 28

    Cannot display query analysis. WP Tuner is not correctly configured.
    ————————————————————————————————————
    What do I have to do to fix this?
    Thanks in advance.

  5. Shimshon:

    Hi, remember me? I didn’t see the results of WP Tuner. I upgraded, but I still do not see any results on my site?

  6. Mr Pete:

    Alexander - StrategieVincenti (#3) and Viktor (#4), thank you for your reports. I’ll have an answer as soon as I duplicate your issues. Please check again soon :)

    Shimshon (#5), thanks for coming back! I have created some debug tools just for your situation. First step: please try setting the Debug Level to 31 and see if you get anything at the bottom of the page. If so, copy the “wpTuner Diagnostics” and paste them here. If that does not work, we need to email privately. I will arrange a time to watch your site while you set another debug level.

    Thank you all. Your reports help me improve WP Tuner, and they help you improve your blog site.

  7. Massimo Belloni:

    Hi Pete,

    Installed your Very Interesting Plugin. Me too fall in the same kind of error of Alexander (…wptunershow.php 276). The query is much bigger than his, and I’ve also tried to see elevating debug level to 31 (but I don’t get an error like him).

    I have a full log ready, but won’t be post here both for avoiding clobbering this site and for security reasons.

    May I send it somewhere to you?

    Many thanks oin advance for any help.

  8. Shimshon:

    Nothing has changed, I do not see any report. The site just seems to load slower

  9. Jay:

    I too get nothing at all at the bottom of the page..any help? Plugin installed and even says its installed successfully on the settings page, I also tried going back to the default kubrik theme to be sure its not a theme thing..any help would be appreciated..

  10. MK (Casey) van Bronkhorst:

    As requested, copying a debug window’s contents to here:
    Do you need a list of plugins from level 31 as well?

    Same error as Massimo Belloni (wptunershow.php 276)
    wptunershow->Parse_Query()
    SELECT DISTINCT
    id,
    post_title,
    GREATEST(start,’2008-11-01 00:00:00′) AS start_date,
    LEAST(end,’2009-01-01 00:00:00′) AS end_date,
    allday,
    1 AS is_event
    FROM wp_posts,wp_ec3_schedule
    WHERE post_status=’publish’
    AND post_type=’post’
    AND post_id=id
    AND end>=’2008-11-01 00:00:00′
    AND start=’2008-11-01 00:00:00′
    AND post_date<’2009-01-01 00:00:00′
    AND post_date

  11. MK (Casey) van Bronkhorst:

    hrm - seems it stripped out some crucial stuff - reposting with a code wrapper - sorry about that

    SELECT DISTINCT
    id,
    post_title,
    GREATEST(start,'2008-11-01 00:00:00') AS start_date,
    LEAST(end,'2009-01-01 00:00:00') AS end_date,
    allday,
    1 AS is_event
    FROM wp_posts,wp_ec3_schedule
    WHERE post_status='publish'
    AND post_type='post'
    AND post_id=id
    AND end>='2008-11-01 00:00:00'
    AND start='2008-11-01 00:00:00'
    AND post_date<'2009-01-01 00:00:00'
    AND post_date

  12. Mr Pete:

    I’ve created a new 0.9.2 version.

    Alexander - StrategieVincenti (#3), MK (Casey) van Bronkhorst (#10), Massimo Belloni (#7), please upgrade. The new version either solves the issue, or should directly pinpoint where the query in question can be found. That will help me track down further trouble.

    Shimshon (#8), Jay (#9) and others who are seeing nothing at all: I will need to work with someone to track this down. Obviously, if you see nothing, it is hard for me to diagnose :) … I have several tools I can use to debug this, but will need a few minutes of your time to work together with me. Please tell me a time we can connect (and what timezone you are in.) We can also use IM or Skype. You can comment here, or email to me at Webbed dot Pete at gmail dot com.

    THANK YOU so much, everyone! You are helping rapidly improve this tool!

  13. Massimo Belloni:

    Hello,

    Updated to V 0.9.2: now no errors appear. Great!

    PS: what is the plugin with “strange query”?

    Thanks!

    Max

  14. Mr Pete:

    Hooray! Thank you everyone for your feedback. Please update to 0.9.3 and I think you’ll be quite happy :)

    I was (finally) able to duplicate the “can’t see anything” problem. Believe it or not, there’s been a bug in WordPress since version 2.5 — when you first install, the admin user’s “user_level” is zero when it should be 10. I’ve worked around that, so users like Shimshon and Jay should find everything working ok.

    I also found a way to identify code locations in older versions of WordPress (before 2.5), so now all users will see code locations in the Timing Report.

    FYI, I’m now running simultaneous test versions of WordPress 2.0.6, 2.3.3, 2.7 beta, the current “trunk”, plus a temp version that I can switch to any release I like.

  15. MK (Casey) van Bronkhorst:

    on NEW release 0.9.3 and debug 1:

    wpTuner Report
    Please report to MrPete. WP Tuner could not match this complex (or possibly invalid) database query. (WP Tuner and your system are still working ok):
    ( SELECT DISTINCT
    id,
    post_title,
    GREATEST(start,'2008-11-01 00:00:00') AS start_date,
    LEAST(end,'2009-01-01 00:00:00') AS end_date,
    allday,
    1 AS is_event
    FROM wp_posts,wp_ec3_schedule
    WHERE post_status='publish'
    AND post_type='post'
    AND post_id=id
    AND end>='2008-11-01 00:00:00'
    AND start='2008-11-01 00:00:00'
    AND post_dateParse_Query() wp-content/plugins/wptuner/wptunershow.php 275

    Also on the new release page it appears comments are closed on the page itself.

  16. Mr Pete:

    Re: MK (Casey) van Bronkhorst (#15), oops… sigh. Wrong comments enabled! MK, what plugin has that query? In 0.9.3 it should say…

  17. MK (Casey) van Bronkhorst:

    not sure what you mean… isn’t it yours? Im using 0.9.3 and debug 1 - shoudl I try something else? that is copied right from your reporting screen. the right column says wptunershow.php 275

  18. MrPete:

    MK (Casey) van Bronkhorst (#17), below the query there should be a filename and line number that’s not in WP Tuner. If not, then please use the “show everything” mode. That will create a table listing every query, and where it is located in the code.

    My goal is to find which plugin contains that query, so I can install the same plugin myself for testing :)

  19. Alexander - Strategie Vincenti:

    Upgraded the plugin.

    The reulsts I get are:

    7.330 DESC wp_comments
    [wp-content/plugins/subscribe-to-comments/subscribe-to-comments.php(734): wpdb->get_col()]

    ciao
    alex

  20. Mr Pete:

    Re: Alexander - Strategie Vincenti (#19), GREAT! That’s a normal DB query, which took 7.33 milliseconds. In the new version, you should not be seeing any errors for a “DESC wp_comments” (i.e. DESCRIBE wp_comments) query.

  21. Mr Pete:

    This thread is now closed. Please visit the current comment thread.

Pages

Blogs

Quick Tip Jar

Currency:

Amount:

Categories

Tags