New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Call to undefined method Piwik\Plugin\Manager::getPluginDirectory() #14250
Comments
Just got this error while upgrading to 3.9.1:
|
Got also on two instances this error... |
After upgrade a 3.8.1 enterprise version to 3.9.0 enterprise version and another upgrade to 3.9.1 enterprise version UI show 3.9.1 but in database, core still in 3.8.1, and plugins like version_MediaAnalytics still in 3.3.1. The archive job won't run because they are missing table :
The ./console core:update didn't return anything I've this php errors After adding It's ok |
Much like Sh4d0wF1gh7, it was fine after returning to the same install script. It was marked as "already updated". Unsure if actually complete however. |
We are still on 3.8.1 because of this problem. Is there an expected date when this will be fixed? |
@larsen0815 This bug has already been fixed with 3.9.1, but as during the update the old code (with the bug) is running, you will still see the error when upgrading to 3.9.1. But the next upgrade from 3.9.1 should then be fine. |
You can simply do a manual three step upgrade (https://matomo.org/docs/update/#the-manual-three-step-update) to avoid the problem. The error is part of the one click updater. |
Ah ok. I was already using that workflow. Upgraded my dev system and got no errors that way. |
Got this error using the 1 click updater from 3.8.1 to 3.12.0. I reloaded the page, was prompted to login, then prompted to run the database update. The upgrade appears to be complete, but I'm wondering if anything was missed. Before trying the one-click updater, we ran the command line version and it reported: ./console core:update Everything is already up to date. Despite running this command on 3.8.1 |
Sadly this error got not fixed with #14236. So if someone updates from 3.8.1 to 3.9.1 he still gets the error.
There is already one forum post about it: https://forum.matomo.org/t/update-from-v3-8-1-to-v3-9-1-failed/32215
I also noticed the problem on my second Matomo instance.
//cc @diosmosis
The text was updated successfully, but these errors were encountered: