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.

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

latest upgrade file permissions incorrect causing server 500 #3869

Closed
anonymous-matomo-user opened this issue Apr 3, 2013 · 2 comments
Closed
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Milestone

Comments

@anonymous-matomo-user
Copy link

Latest upgrade to piwik 1.11.1 had file permissions that caused piwik to trigger a server 500 error.

Setting file permission to 644 ot 755 resolves the problem.

Related forums threads;

http://forum.piwik.org/read.php?2,102540,102570
http://forum.piwik.org/read.php?2,102448

Keywords: server 500, file permissions

@mattab
Copy link
Member

mattab commented Apr 3, 2013

Thanks for the report. The problem is


The permissions on the files (not folders or directories) are not set correctly.
Simply change all the file permissions from 664 to 644 in the piwik main directory. Then you are done. 

That's interesting. Maybe it is a side effect of GIT migration.

I see that the files have 664 in GIT. When i chmod to 644, and then do "git status" the filemode change does not appear. I also tried:
$ git config core.filemode true

So I'm not sure, how we go to modify these file permissions back to 644 in git?

IDEAL Solution: Maybe the ideal fix is to recursively convert all PHP files in Piwik to 644 permission?

@mattab
Copy link
Member

mattab commented Apr 4, 2013

Could you please try with all files from the latest beta, I tried to change umask to 0022 which should fix it. Thanks Fabian for the hint! http://builds.piwik.org/piwik-1.12-b5.zip

@anonymous-matomo-user anonymous-matomo-user added this to the 1.12 - The Great 1.x Backlog milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc.
Projects
None yet
Development

No branches or pull requests

2 participants