Problem/Motivation

in #2466197: Staging directory should not have to be writeable. it was decided that setting the warning on non-writable config directories was just fine. See https://www.drupal.org/node/2466197#comment-11271845 for more on the discussion.

However the config not being writable really shouldn't be a warning level notice, because a) its not actionable on production platforms and b) only configuration import from a tarball requires the folder to be web writable.

Proposed resolution

Remaining tasks

Review the patch.

User interface changes

Non-writable config directories will be reported under the information section instead of a site-wide warning.

API changes

None

Members fund testing for the Drupal project. Drupal Association Learn more

Comments

japerry created an issue. See original summary.

japerry’s picture

Status: Active » Needs review
FileSize
1.44 KB

Patch inc..

geerlingguy’s picture

+1 — it's not only on hosting providers; the default configuration I have for my own production sites doesn't allow writes to the config sync directory, and especially with the redesigned status report page, it always irks me to know I have to scroll down once I see the huge "1 WARNING" label at the top, and then I realize that yes, it's still just the config sync directory.

Dinesh18’s picture

Agree with #3

geerlingguy’s picture

Status: Needs review » Reviewed & tested by the community
Issue tags: +d8ux

May I be so bold... tested on the site in question where I was irked for the last time. The patch applies and makes it so the site has no more warnings.

alexpott’s picture

Status: Reviewed & tested by the community » Needs work

So what happens when you try to upload a tarball to a site where the folder is not writeable?

alexpott’s picture

I.e. I think we should prevent upload on admin/config/development/configuration/full/import with a message when the folder is not writeable.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.