Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Entering Settings doesn't work after update to 2.4.0 #5414

Closed
anonymous-matomo-user opened this issue Jul 4, 2014 · 20 comments
Closed

Entering Settings doesn't work after update to 2.4.0 #5414

anonymous-matomo-user opened this issue Jul 4, 2014 · 20 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Milestone
Backlog (Help wan...

Comments

@anonymous-matomo-user
Copy link

Entering Settings is no loger possible after updating Piwik to 2.4.0.

It stops the connection to the script and the Apache2 log shows exception errors.

Everything else seems to work fine.

There is a thread in the Piwik forums describing the issue:
http://forum.piwik.org/read.php?2,117384
@mattab
Copy link
Member

mattab commented Jul 7, 2014

it seems many users have problem with this, increasing priority.

@anonymous-matomo-user anonymous-matomo-user added this to the 2.5.0 - Piwik 2.5.0 milestone Jul 8, 2014
@geotux
Copy link

geotux commented Jul 9, 2014

Same to me, server log "error: Premature end of script headers: index.php".
All pages of my piwik 2.4.0 are available but not the "settings" page. If i want access "settings" it ends up in internal 500 error page.

@fenta23
Copy link

fenta23 commented Jul 15, 2014

Same here. version 2.4.2
Deleting the file 'piwik/plugins/ExampleUI/ExampleUI.php' doesn't work.

also uncommented the Example Plugins in the config.
; PluginsInstalled[] = "ExampleAPI"
; PluginsInstalled[] = "ExamplePlugin"
; PluginsInstalled[] = "ExampleRssWidget"

will not help.

Any news on this issue?

@mattab
Copy link
Member

mattab commented Jul 15, 2014

We haven't yet been able to reproduce this issue. it would be great if you could provide us access to your piwik server (FTP or SSH) so we could troubleshoot live the error and find the solution. could you please email your credentials and link to this ticket, to benaka@piwik dot org? cc @diosmosis

@itsdun
Copy link

itsdun commented Jul 15, 2014

It seems the problem occured after a automatic update. In my case from 1.* to 2.4.1.
Workaround:
After uploading the current package files (2.4.1) from piwik.org into a new folder and connect it to my existing database, the installation runs as expected.

@Bufallo
Copy link

Bufallo commented Jul 17, 2014

I provided some logfile and js-console screenshots here:
http://forum.piwik.org/read.php?2,117384,page=1#msg-117914

Im using piwik for 1 year now and i always used the autoupdater.

@wedi
Copy link
Contributor

wedi commented Jul 25, 2014

I'm affected, too. My user menu looks like this:

@mattab mattab removed the c: Core label Aug 3, 2014
@mattab mattab modified the milestones: Piwik 2.5.0, Short term Aug 3, 2014
@mattab
Copy link
Member

mattab commented Aug 5, 2014

I'm moving out of 2.5.0 as we have not identified the cause of bug. Please report here if you have an issue. Maybe you could also check in your browser console if there any error message displayed?

@wedi
Copy link
Contributor

wedi commented Aug 6, 2014

The console says logging was deactivated by script on the page, but firebug gave me a lengthy message:

Error: [$injector:unpr] http://errors.angularjs.org/1.2.13/$injector/unpr?p0=piwikApiProvider%20%3C-%20piwikApi%20%3C-%20sitesManagerApiHelper%20%3C-%20coreAPI
E/<@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:6:443
ac/l.$injector<@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:32:119
c@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:30:195
ac/p.$injector<@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:32:189
c@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:30:195
d@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:30:382
ac/p.$injector<@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:32:202
c@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:30:195
d@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:30:382
ac/p.$injector<@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:32:202
c@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:30:195
d@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:30:382
f/<.instantiate@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:31:78
kd/this.$get</<@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:62:413
I/<@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:49:64
r@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:7:363
I@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:48:433
h@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:42:409
Y/<@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:42:102
ue</<.link@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:183:352
I@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:49:397
h@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:42:409
Y/<@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:42:102
ba/<@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:43:337
p@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:47:73
te</<.compile/</</<@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:183:32
q/g.success/<@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:67:279
Bd/e/l.promise.then/B@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:94:1
Bd/f/<.then/<@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:95:163
Cd/this.$get</h.prototype.$eval@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:103:445
Cd/this.$get</h.prototype.$digest@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:101:210
Cd/this.$get</h.prototype.$apply@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:104:262
g@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:68:10
I@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:72:109
qd/</y.onreadystatechange@http://p.dirk-weise.de/libs/angularjs/angular.min.js?cb=25d0a4342df73a2109cf6b8f6fc21a51:73:154

<div class="ng-scope" ng-include="'plugins/SitesManager/templates/index.html'">

@mattab
Copy link
Member

mattab commented Aug 7, 2014

@wedi maybe you could send your Piwik access details to thomas at piwik with a link to this ticket, and maybe he could help you!

tsteur added a commit that referenced this issue Aug 15, 2014
@tsteur
refs #5414 this could fix the segmentation fault. It is more of a gue…
3d547e5 
…ss but I can see in the strace settings could be envolved in this. Anyway, Settings should use findComponents to get the instances. Wondering if a test fails?
tsteur added a commit that referenced this issue Aug 15, 2014
@tsteur
refs #5414 make those settings readable by all users
d0a6e2d
tsteur added a commit that referenced this issue Aug 15, 2014
@tsteur
refs #5414 only find components of actually activated plugins. Wonder…
3dc2e56 
…ing if this breaks any tests? make sure to cleanup plugin settings before uninstalling it. Otherwise cleanupPluginSettings cannot load the plugin
@tsteur
Copy link
Member

tsteur commented Aug 19, 2014

Just FYI: One user was able to fix it by updating from PHP 5.3.6 to PHP 5.5. Of course this is not a solution to fix the actual problem. In case you really depend on this you might want to consider updating PHP to not having to wait.

tsteur added a commit that referenced this issue Aug 19, 2014
@tsteur
refs #5414 this should fix the seg fault on PHP 5.3.6. I did install …
3252814 
…an Apache + PHP 5.3.6 and was able to reproduce
@tsteur
Copy link
Member

tsteur commented Aug 19, 2014

Most likely this patch will fix the problem: 3252814

Feel free to give it a try. Don't forget to clear an opcache after editing the file core/Plugin/Settings.php in case one is used.

@tsteur tsteur closed this as completed Aug 19, 2014
@wedi
Copy link
Contributor

wedi commented Aug 28, 2014

Unfortunately applying 3252814 does not resolve the problem, nor did an upgrade of PHP from 5.4.30 to 5.5.14.
After opening the SitesManager I find the following entries in my server's error log:

[Thu Aug 28 01:53:19 2014] [error] (11)Resource temporarily unavailable: fork: Unable to fork new process
[Thu Aug 28 01:53:29 2014] [error] (11)Resource temporarily unavailable: fork: Unable to fork new process
[Thu Aug 28 01:53:41 2014] [error] (11)Resource temporarily unavailable: fork: Unable to fork new process
[Thu Aug 28 01:53:51 2014] [error] (11)Resource temporarily unavailable: fork: Unable to fork new process

@tsteur
Copy link
Member

tsteur commented Aug 28, 2014

Hi wedi, I am pretty sure this is not related to this issue. I reckon this is rather a server configuration issue. Are you seeing anything at all on this page? Or on any other page in the admin? Is everything else working for you? Would you mind asking for this problem in the forums? http://forum.piwik.org/

I am not 100% sure but I think it is rather a support question than an actual bug. Maybe I am wrong...

@Geck00
Copy link

Geck00 commented Oct 27, 2014

Hey there...
are there any news about this issue? Im having the same problem after the automatic update. And i also checked if changing the php version or applying that patchy thing 3252814 works. But both didnt...
So i would be happy about an update since the last answer in this topic was a while ago...
thx in advance

@tsteur
Copy link
Member

tsteur commented Oct 27, 2014

The issue is closed and it is supposed to work already. Are you using the latest Piwik version? If so, would you mind to create a new issue for this problem? Otherwise update to the latest version and check if it still fails.

@cobrafast
Copy link

I'm on Piwik 2.9.1 (according to the "Help" page) and am still affected by the bug.
I cannot enter the settings page.

Fatal error: Class 'Piwik_Plugin' not found in /var/.../piwik/plugins/ExampleUI/ExampleUI.php on line 27
Fatal error: Uncaught exception 'Exception' with message 'The class ExampleUI couldn't be found in the file '/var/.../piwik/plugins/ExampleUI/ExampleUI.php'' in /var/.../piwik/core/Plugin/Manager.php:937
Stack trace:
#0 /var/.../piwik/core/Plugin/Manager.php(905): Piwik\Plugin\Manager->makePluginClass('ExampleUI')
#1 /var/.../piwik/core/Plugin/Manager.php(571): Piwik\Plugin\Manager->loadPlugin('ExampleUI')
#2 /var/.../piwik/plugins/CorePluginsAdmin/Controller.php(362): Piwik\Plugin\Manager->loadAllPluginsAndGetTheirInfo()
#3 [internal function]: Piwik\Plugins\CorePluginsAdmin\Controller->safemode(Array)
#4 /var/.../piwik/core/FrontController.php(582): call_user_func_array(Array, Array)
#5 /var/.../piwik/core/FrontController.php(96): Piwik\FrontController->doDispatch('CorePluginsAdmi...', 'safemode', Array)
#6 /var/.../piwik/core/FrontController.php(258): Piwik\FrontControl in /var/.../piwik/core/Plugin/Manager.php on line 937

Apparently I cannot reopen this issue.

@tsteur
Copy link
Member

tsteur commented Jan 4, 2015

@cobrafast looks like you updated from a very old Piwik version? It should be fixed by downloading Piwik again from the website and copying all the contained files to your webserver replacing the old ones see http://piwik.org/docs/update/#the-manual-three-step-update . Do not forget to backup your config file as described.

@wedi
Copy link
Contributor

wedi commented Jan 9, 2015

Unfortunately I cannot confirm that replacing all files of a Piwik 2.10.0 installation with a fresh download of 2.10.0 resolves this issue but it changed the behaviour: I don’t get a error message in the apache error log anymore but now I get a blank page with just the menu on the left when opening index.php?module=SitesManager&action=index&idSite=1&period=range&date=previous30.

@tsteur Every other page I tried in the piwik admin is working correctly and so does my WordPress installation. The server configuration is the standard configuration of my host and the server error is gone with the update I did today. I’m going to ask in the forums.

bildschirmfoto 2015-01-09 um 13 42 52
bildschirmfoto 2015-01-09 um 13 43 14

@twenta
Copy link

twenta commented Jun 26, 2016

Pretty old one, but in case someone experiences it while updating...
Updating was successful for me, after I left only
[database]
host = "localhost"
username = "username"
password = "password"
dbname = "piwik"
tables_prefix = "piwik_"
in the config.ini.php

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Projects
None yet
Milestone
Backlog (Help wanted)
Development

No branches or pull requests