-
Notifications
You must be signed in to change notification settings - Fork 117
Allow Drupal 8 to Install in Git Mode #36
Comments
Running my installer locally and commiting the changes, then pushing up to Pantheon solved the problem. The diff was just this line: |
This is a known issue since Drupal 8 requires write access to the settings.php to write this information. Our default is SFTP mode which allows this writability ,but presumably you are in Git mode. Leaving this open until we figure out a way to get this value set in both SFTP + Git mode. |
I wrote a patch which will avoid the problem for all sites based on Distros - https://www.drupal.org/node/2156401. Please help review. |
Yep, I had to switch back to SFTP and was then able to proceed with the install. Perhaps you guys can set the permissions of that directory differently for install? Or at least some help text around this - I figured it out on my own pretty quickly, but less experienced users (or even long-term Drupal folks without Pantheon experience) might not. :-) |
It would be ideal to get Moshe's patch to work in Drupal so we can install in either case, otherwise we can just provide a bit more documentation to tell users that first time installs need to happen in settings.php. |
I could use help with that issue. I ran out of steam and dont plan to return to it. |
The big bug-a-boo here is the question catch raised. If people are really concerned that someone might run into problems by converting a single-distro multisite into a multiple-distro multisite, then the issue will probably never get committed. No one responded to that concern, though; maybe this means the concern is minor enough that it might move forward anyway? At this point, we can install cleanly without it, so the benefit we get is that it would allow us to install in 'git' mode, instead of requiring a switch to sftp mode. I don't think that's critical for us, but I might return there as time permits if it seemed the efforts might be fruitful. |
Looks like this is still an issue. Tried to install a site on Pantheon in git mode and get the following error:
Because the issue got closed I assumed that it got also resolved. What is the current state? |
This issue is open. See also the issue on Drupal.org: https://www.drupal.org/node/2156401. If that is fixed and committed to Drupal core, then installation in "git" mode will work on Pantheon. For now, though, you must switch to SFTP mode before installing. |
Where's the status on this and on relocatable docroot? |
The main problem with this issue is that even once https://www.drupal.org/node/2156401 is committed, it doesn't really help the DX here unless we (a) make a 'Pantheon' distribution in drops-8, or (b) write the 'standard' profile into settings.php. Either of those options would make it inconvenient for folks who want to install the 'minimal' profile. Because of that, we probably won't take any action vis-a-vis 2156401 in drops-8 -- we will inherit this fix once it is committed to Drupal core. Therefore, installing in git mode will only be available for those who update their settings.php prior to installing. Practically speaking, this will probably mostly be folks who set up a custom upstream. |
I've just run into this problem and have not been able to re-run the installer after switching to SFTP in my Pantheon dashboard. 5 minutes into Pantheon and the install failure is compromising - an error as immediate as getting Drupal installed, which completely blocks further progress, creates a poor start for evaluating Pantheon. I chose "minimal" as my Drupal install. Pantheon should not allow users to choose this if it causes an error the user can't easily fix, without warning them or telling them in advance they will have to fix it and how to do so. Alternatively, Pantheon could suppress presenting user with a choice between Git and SFTP until after the install is complete. Using an SFTP tool (Filezilla) to try to manually update settings.php also did not work for me. Neither did pushing my local install (which succeeded). |
@deborah-ufw Can you try again with another site? I was just able to install successfully. If you're still having issues, please contact support. The fix is upstream, not something directly in our control, but since this issue was opened, we added an error message to prompt you to change to Git mode for installation: |
I was also able to install successfully using the minimal installation profile. |
Correct, but now that its been that way long enough to graduate college, I've just learned to live with it :) |
FWIW, my patch was accepted into Drupal core 3 years ago so it may be possible for Pantheon to get past the limitation. And yeah, perhaps its no longer a priority for anyone, given the duration of the limitation. |
Thank you for the patch !! I was amazed to get a notification 5 years after commenting on this thread.
Pantheon may have difficulty evaluating how many potential users have dropped off (and will continue to drop off) when they experience this kind of a failure on an install where the purpose is to evaluate the platform. Blocking first time users is usually a business killer. |
I'd agree, but the platform now warns you specifically about what the cause of the issue is, and I believe it even spins up Drupal 8 sites in SFTP mode, so the experience is not the same as it was when us fledgling D8 developers tried to use the new fancy and hit problems. I think that is why the issue went four years without a comment :) |
Confirmed that I got the notification today while trying to install on git. Just my two cents, I was concerned that switching from git to sftp was going to break something. I didn't feel confident it wouldn't until I found this issue and read the comments. |
Greetings from the future! A fix has been merged so it's no longer necessary to be in "SFTP mode" to install Drupal. The configuration change will roll out gradually to existing sites.. new sites should get it immediately. I'll leave this issue open for a couple days and close it if no issues arise. |
Getting this trying to install Drupal 8 with beta10
Install stops there
The text was updated successfully, but these errors were encountered: