Fatal error on activating (after update)
-
I just got the following error:
Fatal error: Class QM_Output_Html contains 1 abstract method and must therefore be declared abstract or implement the remaining methods (QM_Output::get_type) in /[complete path]/wp-content/plugins/query-monitor/output/Html.php on line 183
here a lot of information about my system, created with system-snapshot-report:
### Begin System Info ###
** WORDPRESS DATA **
Multisite: No
WP Version: 3.8.1
Permalink: /%postname%/
Cur Theme: Twenty Thirteen 1.1
Post Types: post, page, attachment, revision, nav_menu_item, tribe_events, tribe_venue, tribe_organizer
Post Stati: publish, future, draft, pending, private, trash, auto-draft, inherit** WORDPRESS CONFIG **
WP_DEBUG: Disabled
WP Memory Limit: 40MB
Table Prefix: [don’t tell you]
Prefix Length: Acceptable (9 characters)
Show On Front: posts
Page On Front: n/a
Page For Posts: n/a** BROWSER DATA **
Platform: Apple
Browser Name: Firefox
Browser Vers: 27.0
UA String: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Firefox/27.0** SERVER DATA **
jQuery Version 1.10.2
PHP Version: 5.2.17
MySQL Version: 5.5.28-log
Server Software: Apache/2.2.22** PHP CONFIGURATION **
Safe Mode: No
Memory Limit: 256M
Upload Max: 32M
Post Max: 8M
Time Limit: 90
Max Input Vars:
Display Errors: On
Sessions: Disabled
Session Name: PHPSESSID
Cookie Path: /
Save Path: /tmp
Use Cookies: On
Use Only Cookies: Off
FSOCKOPEN: Your server supports fsockopen.
cURL: Your server supports cURL.
SOAP Client: Your server has the SOAP Client enabled.
SUHOSIN: Your server does not have SUHOSIN installed.** PLUGIN INFORMATION **
Active Plugins: (11)
– AntiVirus 1.3.5
– InfiniteWP – Client 1.2.8
– Query Monitor 2.6.5
– Roost Web Push 2.0.2
– Statify 1.2.6
– System Snapshot Report 1.0.0
– The Events Calendar 3.4.1
– Toolbox 0.1
– Under Construction 1.12
– User Switching 0.8.7
– WordPress Plugin Repo Stats 0.1.8Inactive Plugins: (20)
– [lots, as this is a playground site under construction]### End System Info ###
- The topic ‘Fatal error on activating (after update)’ is closed to new replies.