Hi
I get this error message when I try to use the plugin. This happens after I get a number of installations errors with the plugin that tell me there were errors with 'mkdir' command.
Any insight would be appreciated ... I may have not given sufficient user rights to MySQL user ... I have used http://drupal.org/getting-started/6/install/create-database as the template for the user setup. I have also added 'File' to these permissions but this has not helped. All other aspects and modules of Drupal are working normally.
Any help would be appreciated.
Thanks
PseudoMax
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | plugin_install_fail_silently.patch | 776 bytes | jabapyth |
Comments
Comment #1
Anonymous (not verified) commentedAll modules and themes downloaded from drupal.org are compressed. The message "The plugin manager cannot run because neither the tar executable nor the Archive/Tar package could be located." means that your installation does not have any available method of decompressing these files (and thus installing them.) The easiest way to fix that should be to install the Archive/Tar package from PEAR.
Comment #2
PseudoMax commentedHi
I have decompressed the downloaded package with WinRAR and there are no compressed files in the directory. I have done the same with other modules without any problems or similar messages. The files in the directory are: 'ftp.backend.inc', 'LICENSE.txt', 'plugin_manager.module', 'plugin_manager.admin.inc', 'plugin_manager.info', 'plugin_manager.install', 'README.txt', 'ssh.backend.inc'.
Thanks
Comment #3
PseudoMax commentedThis is the error messages I get when trying to install the plugin:
* warning: mkdir() [function.mkdir]: File exists in C:\Program Files\wamp\apps\drupal-6.4\modules\plugin_manager\plugin_manager.install on line 80.
* warning: mkdir() [function.mkdir]: File exists in C:\Program Files\wamp\apps\drupal-6.4\modules\plugin_manager\plugin_manager.install on line 81.
* warning: mkdir() [function.mkdir]: No such file or directory in C:\Program Files\wamp\apps\drupal-6.4\modules\plugin_manager\plugin_manager.install on line 84.
* Could not create directory
* warning: mkdir() [function.mkdir]: No such file or directory in C:\Program Files\wamp\apps\drupal-6.4\modules\plugin_manager\plugin_manager.install on line 88.
* Could not create directory C:/Program Files/wamp/www//drupal/sites/all/themes
Comment #4
jabapyth commentedThe reasons you get this error are
A) You are running windows (not Unix), so Plugin Manager can't take advantage of the Unix command "tar" to extract the files.
B) Your PHP install doesn't have the nessesary libraries to handle the extraction itself.
The way to solve this is either switch to linux, or use PEAR to install the Tar PHP library.
To install pear, go to this page: http://pear.php.net/manual/en/installation.getting.php
then run "pear install Archive_Tar" from the command line.
That should fix it for you.
Good Luck,
Jabapyth
Comment #5
PseudoMax commentedThanks Jabapyth & JoshuaRogers
Will give PEAR a go ...
Comment #6
PseudoMax commentedInstalled PEAR.
I still get the 'mkdir' errors on installation but the module appears to be working correctly ... ('The plugin manager cannot run because neither the tar executable nor the Archive/Tar package could be located.' error has disappeared and I now am told: 'The repository is out of date and will be updated.')
If I don't get any further issues ... then thanks again ...
Comment #7
jabapyth commentedIt turns out there was a small bug (the reason for your mkdir errors). That bug has been fixed by this patch.
I added "@" in front of the mkdir commands, allowing them to fail silently (so they don't show the user that ugly error). Because we check whether they were successful directly after, silent failure is not a problem.
The patch is attached.
Comment #8
Anonymous (not verified) commentedThe patch looks good. I'll commit it asap. (Granted that actually means hopefully within the next day) ;)
Comment #9
jabapyth commentedive got it covered
Comment #10
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.