WPIntell

Source evidence

sends a 500 error

Query Monitor · support · 2026-02-10T15:17:00+00:00

Query Monitor plugin evidence original source source API
mixedsentiment
mediumseverity
0.85relevance
4replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 35 rows with source links

17.1% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

29 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
mbdireccion resolved
I´ve installed your plugin three times, added define( ‘QM_DISABLE_ERROR_HANDLER’, true ); in my wp-config.php and always has sent this 500 error in my dashboard. The error comes if you close session and log again. In that moment you can not log anymore. Can you help me to install it, pleas? What’s the error in your PHP error log that triggers the 500? Thanks for your reply. I´ve seen the errors and it was the SecResponseBodyLimit. I´ve set theese Additional Apache directives foir HTTP and HTTPS just for this domain: SecResponseBodyLimit 5242880 SecResponseBodyLimitAction ProcessPartial Do yout hink is all right? I see, so you were attempting to reduce the amount of data returned by QM due to the large body size. Over 5MB means your site is probably performing a large amount of database queries as well as PHP errors and everything else. I can’t comment on whether SecResponseBodyLimit is the right config to change for your server, give it a try and see how it goes. The next version of QM will address this somewhat by switching away from server-side rendering of all the HTML tables that contribute to this output size. If you’re curious you can download the alpha version here , although it’s still under heavy testing. Thanks a lot ant thanks for such your great pulgins as this one and Cron Jobs.

Comments

4 shown
John Blackbourn 2026-02-10T17:04:00+00:00

What’s the error in your PHP error log that triggers the 500?

mbdireccion 2026-02-10T19:23:00+00:00

Thanks for your reply. I´ve seen the errors and it was the SecResponseBodyLimit. I´ve set theese Additional Apache directives foir HTTP and HTTPS just for this domain: SecResponseBodyLimit 5242880 SecResponseBodyLimitAction ProcessPartial Do yout hink is all right?

John Blackbourn 2026-02-11T12:19:00+00:00

I see, so you were attempting to reduce the amount of data returned by QM due to the large body size. Over 5MB means your site is probably performing a large amount of database queries as well as PHP errors and everything else. I can’t comment on whether SecResponseBodyLimit is the right config to change for your server, give it a try and see how it goes. The next version of QM will address this somewhat by switching away from server-side rendering of all the HTML tables that contribute to this output size. If you’re curious you can download the alpha version here , although it’s still under heavy testing.

mbdireccion 2026-02-12T08:49:00+00:00

Thanks a lot ant thanks for such your great pulgins as this one and Cron Jobs.