I have tried to use the update system on a system where the FTP logins appear to be chrooted to the account's home directory.
This breaks the automatic module install/update system in the following manner:
update.module expects the FTP path for a module to match the data retrieved from what php tells it. In this instance, /home/.sites/123/site45/web/sites/all/modules/
The FTP's chroot has the structure as /web/sites/all/modules/
When Drupal tries to chdir to /home/.sites etc, which ~does not exist~ with the chroot setup, the updates fail.
-- Suggested Fix:
Allow admin to be able to specify the FTP path ( either in the update settings, or on the page where one enters the ftp login) to get to the drupal installation so the update process can be completed.
To recap: Dupal should not always trust the paths that it gets from PHP for determining FTP paths -- there needs to be a way for the user to verify/correct in cases like these.
Comments
Comment #1
bfroehle CreditAttribution: bfroehle commentedThe chroot should be automatically detected by FileTransfer::findChroot. Let's try to figure out why this is not working...
Comment #2
clarjon1 CreditAttribution: clarjon1 commentedI've taken a look at the logs ( /var/log/messages ) when drupal is running, and this is the output:
Is there some code I can inject (temporarily) into the drupal core files that I can use to get a more in-depth look at the FTP connection?
Comment #3
Bojhan CreditAttribution: Bojhan commentedA bug, but not a biggie.
Comment #4
controla CreditAttribution: controla commentednot a biggie but certainly needs a fix, any update on this? just been bitten by it.
Comment #5
pepe000 CreditAttribution: pepe000 commentedversion 7.20 - bug still occurs