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

Can't setup with non-writable htaccess #34471

Closed
PVince81 opened this issue Feb 12, 2019 · 4 comments · Fixed by #34478
Closed

Can't setup with non-writable htaccess #34471

PVince81 opened this issue Feb 12, 2019 · 4 comments · Fixed by #34478
Assignees
Labels
p2-high Escalation, on top of current planning, release blocker regression Type:Bug
Milestone

Comments

@PVince81
Copy link
Contributor

As far as I remember, some setups are configured fully read-only, or some admins don't want to let the web server write anything in the PHP tree, so they disable it.

We should allow non-writable htaccess.

This PR #32230 makes it throw an exception.

We should soften it and output a warning on the console when it happens.

@individual-it

@PVince81
Copy link
Contributor Author

reading https://doc.owncloud.org/server/10.0/admin_manual/configuration/server/index_php_less_urls.html?highlight=htaccess#prerequisites seems to imply that having htaccess non-writable is also ok. you only need to make it writable if you want this extra thing.

@PVince81 PVince81 added the p2-high Escalation, on top of current planning, release blocker label Feb 12, 2019
@ownclouders
Copy link
Contributor

GitMate.io thinks possibly related issues are #32230 (throw exception when .htaccess file is not writable), #34461 ([stable10] throw exception when .htaccess file is not writable), #18260 (Cannot setup stable8), #23207 (.htaccess RewriteRule brakes non-standard alias), and #25755 (home storage not writable).

@individual-it
Copy link
Member

exception should not be thrown on installation or update but only on occ maintenance:update:htaccess
whoever does that clearly wants to update the htaccess file and if that fails an exception should be thrown

@individual-it
Copy link
Member

PR here #34478

@lock lock bot locked as resolved and limited conversation to collaborators Feb 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
p2-high Escalation, on top of current planning, release blocker regression Type:Bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants