Fatal Error on 3.1.1.

  • Resolved HKP

    (@hiskingdomprophecy)


    6 years ago

    Hi Folks,
    I just upgraded from 3.1.0 to 3.1.1 and got the red fatal error message from your plugin – though all still seems to work…
    I rolled back to the previous version but the error still remains. I see that it has also changed the old version appearance – so I guess I need to do a full reinstallation of the old one, instead of just a rollback, to get it back in order again.
    Thanks,
    Angus

    The QM redacted error message is:

    Fatal error: Uncaught TypeError: Argument 1 passed to QM_Output_Html_Assets::get_dependency_data() must be an instance of _WP_Dependency, boolean given, called in /home/<< path redacted >>/query-monitor/output/html/assets.php on line 122 and defined in /home/<< path redacted >>/query-monitor/output/html/assets.php:140 Stack trace: #0 /home/<< path redacted >>/query-monitor/output/html/assets.php(122): QM_Output_Html_Assets->get_dependency_data(false, Object(WP_Styles), ‘styles’) #1 /home/<< path redacted >>/query-monitor/output/html/assets.php(92): QM_Output_Html_Assets->dependency_rows(Array, Object(WP_Styles), ‘Header’, ‘styles’) #2 /home/<< path redacted >>/query-monitor/dispatchers/Html.php(191): QM_Output_Html_Assets->output() #3 /home/<< path redacted >>/query-monitor/output/html/assets.php on line 140

    ***end***

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

    (@johnbillion)

    WordPress Core Developer

    This is likely caused by another plugin (or theme) on your site.

    Can you try deactivating all your other plugins one by one to see if you can identify the plugin that’s causing the problem? Try switching to one of the default themes too, such as Twenty Seventeen.

    Thread Starter HKP

    (@hiskingdomprophecy)

    @johnbillion
    Thanks John!
    Yes, it was another plugin which updated at the same time as yours.
    They just now posted a further update and on installation, all issues ended.

    Just one little suggestion to the WordPress Core Team:
    Now that many of the core and security updates are automatic, it is possible to have WP generated a local log listing all the core and plugin update versions and dates?
    That would make it easier to start hunting for conflict culprits.

    Regards and thanks,
    Angus

    Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    You could try an audit trail plugin such as Simple History or Stream.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Fatal Error on 3.1.1.’ is closed to new replies.