Title: PHP Errors Not Showing
Last modified: May 19, 2020

---

# PHP Errors Not Showing

 *  [akiai](https://wordpress.org/support/users/akiai/)
 * (@akiai)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/php-errors-not-showing/)
 * “PHP Errors” tab is totally blank. There are a lot of errors (176), which may
   be cause for concern? However Slow Queries and Duplicate Queries tabs show content.
 * Please advise? (see image below)
 * > [View post on imgur.com](https://imgur.com/olQzc63)

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Thread Starter [akiai](https://wordpress.org/support/users/akiai/)
 * (@akiai)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/php-errors-not-showing/#post-12857079)
 * To add some further information:
 * I have just switched my local version to a vanilla TwentyTwenty theme, disabled
   all plugins and placed the following code:
 *     ```
        if ($test) {
           return;
         }
       ```
   
 * The 1 php error shows but again the field is blank.
 * On running a ctrl + f for an “undefined index” error, I’m able to find that the
   error does indeed exist.
 * But for some reason the CSS is set to:
 *     ```
       #query-monitor-main .qm-hide,
       #query-monitor-main .qm-hide-scripts-dependencies,
       #query-monitor-main .qm-hide-styles-dependencies,
       #query-monitor-main .qm-hide-scripts-dependents,
       #query-monitor-main .qm-hide-styles-dependents,
       #query-monitor-main .qm-hide-scripts-host,
       #query-monitor-main .qm-hide-styles-host,
       #query-monitor-main .qm-hide-user,
       #query-monitor-main .qm-hide-result,
       #query-monitor-main .qm-hide-name,
       #query-monitor-main .qm-hide-type,
       #query-monitor-main .qm-hide-caller,
       #query-monitor-main .qm-hide-component {
         display: none !important;
       }
       ```
   
 * Which is hiding all the errors. I have no idea how or why this CSS is in place.
 * Is there any way for me to remove the offending CSS? Is there a setting I’ve 
   mistakenly hit?
    -  This reply was modified 5 years, 10 months ago by [akiai](https://wordpress.org/support/users/akiai/).
 *  Plugin Author [John Blackbourn](https://wordpress.org/support/users/johnbillion/)
 * (@johnbillion)
 * WordPress Core Developer
 * [5 years, 10 months ago](https://wordpress.org/support/topic/php-errors-not-showing/#post-12857981)
 * Are there any JavaScript errors showing on the page?
 * Can you run `localStorage.clear()` in your web browser’s developer console and
   then reload the page? I’m not sure what’s going wrong there but it looks like
   the filter is broken.
 *  Thread Starter [akiai](https://wordpress.org/support/users/akiai/)
 * (@akiai)
 * [5 years, 10 months ago](https://wordpress.org/support/topic/php-errors-not-showing/#post-12858033)
 * Thanks for the response. `localStorage.clear()` didn’t do the job. Same problem
   persists in both Chrome and Firefox.
 * It’s not a major problem as I just remove the `display: none` styling if I ever
   need to see the errors. Stylesheet being referenced is indeed from Query Monitor
   and not anywhere else. I’ve also disabled all other plugins and tested.
 * Very strange!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘PHP Errors Not Showing’ is closed to new replies.

 * ![](https://ps.w.org/query-monitor/assets/icon.svg?rev=2994095)
 * [Query Monitor - The developer tools panel for WordPress](https://wordpress.org/plugins/query-monitor/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/query-monitor/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/query-monitor/)
 * [Active Topics](https://wordpress.org/support/plugin/query-monitor/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/query-monitor/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/query-monitor/reviews/)

 * 3 replies
 * 2 participants
 * Last reply from: [akiai](https://wordpress.org/support/users/akiai/)
 * Last activity: [5 years, 10 months ago](https://wordpress.org/support/topic/php-errors-not-showing/#post-12858033)
 * Status: not resolved