This plugin could not be loaded correctly and is stopped in restore mode.

@tanrim Do you still see this error? Was Matomo installed successfully? If you see this only during installation this might be expected.

If you still see this error, and you can view the system report in the WordPress Dashboard => Matomo Analytics => System Report
could you send us the anonymised system report from the beginning of that page to wordpress at matomo dot org? If it fails to load the system report page, you may need to enable the safe mode see : https://matomo.org/faq/wordpress/i-have-a-problem-how-do-i-troubleshoot-and-enable-wp_debug/

By adding this to your wp-config.php

define( ‘MATOMO_SAFE_MODE’, true );

I sent you the system report.

I downloaded the beta from your site a few days ago, installed and activated it without problems. (I uninstalled it afterwards.)

Matomo Analytics was successfully installed, but cannot be activated. The attempt to activate it results in a crash of the site with the error-message: “There was a critical error on your website.”
In restore mode you can see the following error message:

This plugin could not be loaded correctly and is stopped in restore mode.

WordPress-Database-Error: [Table ‘[…].wp_matomo_option’ doesn’t exist]
SELECT option_value, option_name FROM wp_matomo_option WHERE autoload = 1

Fatal error: Uncaught Zend_Db_Statement_Exception: WP DB Error: [1146] Table ‘[…].wp_matomo_option’ doesn’t exist SQL: SELECT option_value, option_name FROM wp_matomo_option WHERE autoload = 1 in […]/wp-content/plugins/matomo/classes/WpMatomo/Db/WordPress.php:311 Stack trace: #0 […]/wp-content/plugins/matomo/classes/WpMatomo/Db/WordPress.php(323): Piwik\Db\Adapter\WordPress->after_execute_query(Object(wpdb), ‘SELECT option_v…’) #1 […]/wp-content/plugins/matomo/app/core/Db.php(297): Piwik\Db\Adapter\WordPress->fetchAll(‘SELECT option_v…’, Array) #2 […]/wp-content/plugins/matomo/app/core/Option.php(267): Piwik\Db::fetchAll(‘SELECT option_v…’) #3 […] in […]/wp-content/plugins/matomo/classes/WpMatomo/Db/WordPress.php on line 311

• This reply was modified 4 years, 9 months ago by Tanrim.

> I downloaded the beta from your site a few days ago, installed and activated it without problems. (I uninstalled it afterwards.)

Just to better understand. Did anything change if it worked initially? You basically uninstalled it and then installed it again?

Do you mind maybe trying to delete all Matomo data see https://matomo.org/faq/wordpress/how-do-i-delete-or-reset-the-matomo-for-wordpress-data-completely/ or alternatively https://matomo.org/faq/wordpress/how-do-i-manually-delete-all-matomo-for-wordpress-data/ and then install it again to see if it works then?

Yes, I installed, tried and uninstalled the last beta (0.41?) and installed this plugin. I don’t see what could have changed.

I followed your instructions, but nothing has changed.

I looked at the database and noticed that no tables were created by Matomo.
Next, I searched for entries from matomo and deleted the following:

external_updates-matomo

wp_wfKnownFileList (several thousand entries)
wp_wfFileMods (several thousand entries)

Now it works again!

Awesome, thanks for that. I suppose you wouldn’t know removing which of these 3 different kind of entries made it work in the end? Where they in the wp_option table or is eg wp_wfFileMods its own table?

The wp_wf* entries seem related to WordFence. Will try and reproduce this next week to see if we can improve something there.

@tanrim I’ve installed WordFence and noticed the tables and it’s content etc. I couldn’t quite reproduce the issue but I think what could eg happen is that:

* The beta plugin was initially not on the WordPress directory but downloaded and updated through our servers
* Then the plugin was put on the WordPress directory and WordFence must have blocked something maybe or so. I’m still not 100% sure how WordFence works re the scanned files but I see it compares it against the WordPress directory etc.

I will create a new FAQ tomorrow or the day after and document this behaviour in case it happens again and then we’ll investigate further. I’m glad it works now. Be great if you could mark the issue as resolved.

Thanks!