Here's what i got:

Could not create directory
Could not create directory /usr/local/nginx/html/sites/all/themes

My drupal folder is /home/xxx/www
After that, when trying to install something, PM fails to detect drupal's root folder even if i put the correct path on ftp settings.

Comments

cosmotopper’s picture

cosmotopper commented

I am attempting to install a module 'comment_notify', and I get the following messages:

-- unable to create directory comment_notify/
-- unable to install comment_notify

The 'FTP Path' is set to this absolute reference: /usr/local/data1/aash

The terminology on the settings page is confusing: not sure what 'ftp home' refers to. Also, in the example you suggest '/www', but it appears that is assumed to be a relative path based on the other references in the example. If the path is written as a relative path (with no leading '/'), what is it relative to? If the path is an absolute path (with leading '/') does the module treat it as absolute?

Thanks for any help.

cosmotopper’s picture

cosmotopper commented

I'm new to Drupal, so I'm not familiar with SOP regards pending bugs. After messing around with plugin_manager/ftp.backend.inc, it appears that either ftp_mkdir() or ftp_chmod() is not working right and there seems to be an issue relating to:

FileTransferFTPWrapper (file stream) class (http://drupal.org/node/612546)

As it stands now, it appears the plugin_manager doesn't work. There are some anomalies having to do with the name of the module directory which might be to blame, or it's possible that AppArmor ACL lists or FTP configuration issues are preventing the plugin from creating the module directory in sites/all/modules/.

My main question: is anyone actively maintaining this module, or should I fall back on an external fix?

Thanks.