Query Monitor conflict

  • Resolved Sabrina Zeidan

    (@sabrinazeidan)


    4 years, 7 months ago

    Hey!
    Cool plugin, thank you! Very nice interface.
    Just to let you know: when Query Monitor is enabled, it generates an output in the footer of the page (frontend), which is available to admin only.
    But SEOPress considers this being an actual content though.
    For instance, it gives a warning about about another <h1> on the page and counts its text as a part of the post.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Benjamin Denis

    (@rainbowgeek)

    Hi,
    thank you for your feedback!

    We’re aware of this issue, still looking for a solution.

    Thread Starter Sabrina Zeidan

    (@sabrinazeidan)

    Just a quick thought. May be, dynamically filtering a user’s capabilities can do a trick? Query Monitor uses view_query_monitor capability to let users see that content. Before SEOPress grabs the page content for analysis it can be disabled, and then enabled back.

    add_filter( 'user_has_cap', 'sp_qm', 10, 3);
function sp_qm( $allcaps, $caps, $args ) {
		$allcaps['view_query_monitor'] = false; 
	return $allcaps;
}

//SEOPress grabs the content

remove_filter( 'user_has_cap', 'sp_qm', 10, 3);
    Thread Starter Sabrina Zeidan

    (@sabrinazeidan)

    * For Multisite it should be a bit different

    Plugin Author Benjamin Denis

    (@rainbowgeek)

    Hi,
    could be an idea, thank you for the suggestion ??

    Plugin Author Benjamin Denis

    (@rainbowgeek)

    Available in the next update!

    Thread Starter Sabrina Zeidan

    (@sabrinazeidan)

    That’s cool! Thank you ??

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Query Monitor conflict’ is closed to new replies.