@cqwww opened this Issue on October 14th 2014

Fatal error: Class Piwik\Plugins\Login\Auth contains 4 abstract methods and must therefore be declared abstract or implement the remaining methods (Piwik\Auth::getLogin, Piwik\Auth::getTokenAuthSecret, Piwik\Auth::setPassword, ...) in /plugins/Login/Auth.php on line 250

I get this even trying with a new browser/session or in an existing one from before the upgrade:
Session must be started before any output has been sent to the browser; output started in /plugins/Login/Auth.php/250

@Spone commented on October 14th 2014

same here:

A fatal error occurred

The following error just broke Piwik (v2.8.0):

Class Piwik\Plugins\Login\Auth contains 4 abstract methods and must therefore be declared abstract or implement the remaining methods (Piwik\Auth::getLogin, Piwik\Auth::getTokenAuthSecret, Piwik\Auth::setPassword, ...)

in

/var/www/html/plugins/Login/Auth.php line 250

PHP version: 5.5.9

@diosmosis commented on October 14th 2014 Member

How did you update Piwik? Did you try clearing any php caches that might be in use (ie, opcache/apc)?

@Spone commented on October 14th 2014

I used the autoupdater linked from the upgrade notice (on my Piwik admin panel). I tried to restart Apache, which did not solve the problem. I did not configure any PHP cache.

@diosmosis commented on October 14th 2014 Member

Can you check in plugins/Login/Auth.php whether it has a line "public function getLogin()"? If not, then the updater didn't copy the files correctly. In this case overwriting the files w/ http://builds.piwik.org/latest.zip contents (make sure to keep config/config.ini.php) should fix it.

@Spone commented on October 14th 2014

There is no public function getLogin() in plugins/Login/Auth.php
So I did what you recommended, and this fixed it. Thanks!
Is there something I should have done to prevent breaking my Piwik install?

@diosmosis commented on October 14th 2014 Member

I don't think so, the auto updater should've just overwritten the file, I don't know why it didn't. It's probably a rare bug in the auto updater.

This Issue was closed on October 15th 2014
Powered by GitHub Issue Mirror