Support » Plugin: Query Monitor » QM displaying on Login page

  • Only recently noticed that we’re getting a Query Monitor bar at the bottom of the wp-login page but not always. Twice I’ve noticed it when trying to access /wp-admin and my session has expired so I’m redirect to wp-login.
    I haven’t set the authentication cookie, so as far as I’m aware QM shouldn’t be displaying as I’m not logged in.
    We do run via cloudflare, but have a rule /wp-* bypasses cache. We also use redis object caching but I don’t think either are impacting. I can see the conditions:
    True Conditionals
    is_ssl()
    False Conditionals
    is_404()is_admin()is_archive()is_attachment()is_author()is_blog_admin()is_category()is_comment_feed()is_customize_preview()is_date()is_day()is_embed()is_favicon()is_feed()is_front_page()is_home()is_month()is_network_admin()is_page()is_page_template()is_paged()is_post_type_archive()is_preview()is_privacy_policy()is_robots()is_rtl()is_search()is_single()is_singular()is_sticky()is_tag()is_tax()is_time()is_trackback()is_user_admin()is_year()

    On the Request I can see:
    Response
    Queried Object
    none

    Current User
    Current User: #1

    Request Data
    Remote IP {my ip address}
    HTTP method GET
    Requested URL https://www.{site}.co.uk/wp-login.php?redirect_to=https%3A%2F%2F{site}.co.uk%2Fwp-admin%2F&reauth=1
    * I’ve blanked out the site and IP.

    I’ve tried to replicate it by logging out but the bar seems to then not be there, so I guess logout is clearing a cookie or something while an expired session isn’t.
    I don’t really know where to start to make sure that’s the case.
    IF it’s only displaying because I was an admin logged in then I can live with it, in fact it may be handy. but concerned if it’s cached somewhere that it may be displaying to others. I’ve looked through the info and there’s nothing really bad, plugins, table names, etc that we’d prefer not broadcast to the world not really top secret.

    Only reporting as it seems like it’s something it shouldn’t be doing.

Viewing 1 replies (of 1 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    I’ve seen this occasionally in the past but I haven’t been able to track down the problem either. I think it must be something specific to WordPress rather than QM because QM doesn’t do anything special with regard to user sessions (unless you’ve set the authentication cookie, which you already mentioned).

    I wonder whether the object cache could be to blame. I use Redis too so I’ll see if I can fid some time to look into it.

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.