Stop locking me out of my own sites/default directory if Drupal is already insecure

Created on 24 February 2013, almost 12 years ago
Updated 30 March 2023, over 1 year ago

I know that we change the permissions on settings.php (actually, the default directory) for "security reasons" but it's a change that makes me very mad at drupal on a weekly basis.

Not only does this behavior end up locking unsuspecting newbies out of thier own files - but it also frustrates people working on core (or trying to work on core) since doing a git pull will fail miserably when it gets to a file or directory that's had it's permissions changed - crapping out a bunch of half pulled files all over your hard work, and making it nearly impossible to get back to the pre-crapped-on state.

If we want more contributors to core, we need to fix this annoying behavior of Drupal thinking it knows better than we do about our file permissions.

πŸ“Œ Task
Status

Active

Version

9.5

Component
BaseΒ  β†’

Last updated about 1 hour ago

Created by

πŸ‡ΊπŸ‡ΈUnited States jenlampton

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024