Closed (outdated)
Project:
Drupal core
Version:
8.4.x-dev
Component:
install system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
29 Sep 2014 at 12:20 UTC
Updated:
21 Oct 2017 at 03:01 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
john morahan commentedUntested patch.
Comment #2
john morahan commentedComment #3
andrefy commentedTested
Comment #4
andrefy commentedComment #6
jcuello commentedHi, I've tried to apply the patch at #1But it does not apply.
Comment #7
pythagory commentedComment #8
pythagory commentedRe-rolled patch. Resolved merge conflict with updated services.yml check/warning in core/lib/Drupal/Core/Installer/Form/SiteConfigureForm.php
Comment #11
john morahan commentedComment #12
sushantpasteIt works fine. Patch with minor formatting fix.
While testing this issue , I am not getting" installer instruction to create services.yml and make it writable " (getting only for settings.php file) I am not sure if I have missed anything for installation, can someone check this?
Comment #13
shwetaneelsharma commented@sushantpaste: I guess you were re-installing drupal8 by renaming settings.php file. I don't think you will receive a message for services.yml if it is already present (created) in the directory.
Comment #14
sushantpaste@shwetaneelsharma: Thanks. Yes I am reinstalling drupal8. So I think the patch works fine. If you reviewed patch can you marked it as RTBC.
Comment #15
shwetaneelsharma commentedPatch "installer_doesn_t_warn-2346803-12.patch" passes testing. Installer does warn about writable services.yml file also along with settings.php during the installation process. Attaching screenshot for passed result.
However, I would like to address a new problem here. Before I proceed with the final step of installation here, I am making both the files settings.php and services.yml read only. Now, after hitting the save/continue button, I am seeing the warning displayed for both the files on homepage. Attaching a screenshot.
This shouldn't happen because I had taken away the permissions before finishing the installation. Should this problem be addressed here or in a new ticket?
Thanks,
Shweta.
Comment #16
john morahan commentedActually, it looks like #12 is correct. Since #2547447: Stop creating services.yml by default the installer no longer requires this step at all.
So I think this issue can be closed, right?
Comment #21
nickdickinsonwilde