Plugin could not be activated because it triggered a fatal error

  • Resolved Stuart Neilson

    (@stufreeze)


    4 years, 11 months ago

    We’ve updated the plugin to the latest version (3.5.2) and when we try to deploy it on our staging or production server we get the following error.

    Fatal error: Class QM_Collector_Admin contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (QM_Collector::name) in /www/imgtec_915/public/wp-content/plugins/query-monitor/collectors/admin.php on line 114

    Have you seen this before and any ideas how we get round this issue?

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

    (@johnbillion)

    WordPress Core Developer

    I wonder if your update or installation went wrong because QM_Collector_Admin doesn’t include any abstract methods. Can you try deleting the plugin entirely and reinstalling it?

    Similar problem to report. It started about 4 days ago perhaps when we received the updated version? We recently upgraded to PHP 7.3, fwiw.

    Class QM_Collector_Raw_Request contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (QM_Collector::name) in /dom25404/wp-content/plugins/query-monitor/collectors/raw_request.php on line 81

    Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    I bet this is due to a stale opcode cache after the plugin update. Are you using Zend OPCache? If so, can you try flushing it?

    I have the same error:

    PHP Fatal error: Class QM_Collector_Raw_Request contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (QM_Collector::name) in /wp-content/plugins/query-monitor/collectors/raw_request.php on line 0

    I can see that there is “abstract public function name();” in class QM_Collector

    • This reply was modified 4 years, 10 months ago by eXalted.
    Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    Can you try deleting the plugin entirely and reinstalling it? That method no longer exists.

    I thought I checked that…

    Yes, it’s fixed now. Thank you!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Plugin could not be activated because it triggered a fatal error’ is closed to new replies.