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

File extraction with incorrect 666 permissions #882

Closed
awucweb opened this issue Aug 1, 2016 · 2 comments
Closed

File extraction with incorrect 666 permissions #882

awucweb opened this issue Aug 1, 2016 · 2 comments

Comments

@awucweb
Copy link

awucweb commented Aug 1, 2016

As reported via email to George Dawoud - When the latest build 2.1.8 was extracted on a shared sever the default file permission is set to 666 which results in a 403 permission denied error. To correct this I changed permissions to 644 and could proceed with setup.

@DawoudIO DawoudIO added this to the 2.2.0 milestone Aug 1, 2016
@DawoudIO DawoudIO self-assigned this Aug 1, 2016
@crossan007
Copy link
Contributor

I may be wrong on this, but I believe that ZIP files do not maintain permissions: http://stackoverflow.com/questions/10735297/maintain-file-and-folder-permissions-inside-archives

Therefore, when extracting the files, the application administrator [you] must make sure that the permissions are correct.

@DawoudIO DawoudIO closed this as completed Aug 4, 2016
@DawoudIO DawoudIO removed this from the 2.2.0 milestone Aug 4, 2016
@awucweb
Copy link
Author

awucweb commented Aug 8, 2016

For your interest - Extracted 2.2.0-RC1.zip on server and still had 666 on files. Also discovered that folder permissions 777 were also bringing up 403 error changed to 755 and could access 'Email' and 'Sunday School' links.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants