Active
Project:
Plugin Manager
Version:
6.x-1.10
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Oct 2008 at 15:55 UTC
Updated:
17 Feb 2010 at 20:16 UTC
Jump to comment: Most recent file
Hi there, Just tried this module on a site that did not have it installed previously and got the following error messages:
- Cannot install plugin of type
- Unable to install img_assist
Looking at the filesystem, I can see that the tar.gz files have been downloaded, but not extracted.
I am also getting the same error on one other site on the same server, but on a third install, it is working (but spewed out warnings which I cannot remember over files already existing...).
| Comment | File | Size | Author |
|---|---|---|---|
| #22 | Picture 17.png | 20.93 KB | bigsurs |
| #22 | Picture 19.png | 35.7 KB | bigsurs |
| #22 | Picture 20.png | 31.54 KB | bigsurs |
Comments
Comment #1
ari-meetai commentedExact same happening here. Just that with another plugin: swftools
Comment #2
berdirThe problem is that this module does not exist or does not have D6 compatibility listet at this list:
http://updates.drupal.org/release-history/project-list/all
Plugin Manager does only install modules listed there. So, this is not directly a problem of plugin_manager.
However, plugin_manager should do a better check to see if there is actually a matching row in the database and deny the installation of this module from the beginning.
Comment #3
naheemsays commentederm... ACL IS listed on there... so is Views, so I doubt this is the problem (unless that list has been updated to include those modules since yesterday).
The module it mentions cannot be installed is always the first one in the list of updates selected to install. Removing that from the list just moves to the next one.
This may be a problem with new installs only as for the existing install where it did not work, I did delete all the settings and reinstall the module.
Comment #4
naheemsays commentedJust to be on the safe side, I tied to update Views on its own. Still got the same error.
Comment #5
jabapyth commentedI think the problem is with the way plugin_manager stores plugin types. Could you inspect your msql database?
look in the table "plugin_manager_taxonomy", where short_name is "views" (or whatever).
Comment #6
naheemsays commentedAll three "plugin_manager_*" tables are empty in the two installs where I cannot install anything. They do have contents in the third install (which started off as plugin_manager 1.2 without a deletion of the old data) where the updates work but with warnings of duplicate/existing files.
Comment #7
berdirDid yo actually load the database with admin/plugin_manager/reload atleast once ?
Comment #8
naheemsays commentedNope - did not know about that function and since both failing installs should have been functioning as a new install, I should not have needed to. Good to know now though and running that first, the updates worked.
Should getting the database/reload not be automated? If so, this is a feature request :P
Comment #9
naheemsays commentedJust trying to update Vertical Tabs, but even hitting admin/plugin_manager/reload makes no difference on this occasion
Comment #10
Antinoo commentedsame issue here, I think it's a critical bug. :(
I'll deep into the source code as soon as possible.
Comment #11
Antinoo commentedSince {plugin_manager_taxonomy} is empty, I replaced the
$row = db_fetch_array( ... )line with$row['tag'] = 'modules';, tried to update the feedapi_mapper module and it said "Successfully installed feedapi_mapper".In fact, however, it doesn't seem the module has been updated.
Comment #12
Antinoo commentedIn the ftp_plugin_manager_copy_library() function, in ftp.backend.inc file, I simply added a '/' to the beginning of $ftp_path when plugin_manager is guessing the chrooted path:
and it's working now: it has correctly updated views, panels and several other modules to their lastest version.
Then, it seems it's a path issue.
Please check it, and sumbit a better solution than mine. ;)
Greetings, Giovanni
Comment #13
jabapyth commented@Antinoo
if that fixed it, weren't you getting an error before about 'Could not guess the ftp directory for drupal.'?
@nbz: are you still getting those errors (and have you updated to the latest CVS version)?
Comment #14
naheemsays commentedAre the CVS version and 1.3 not the same?
I manually updated the vertical_tabs module, so I no longer have a test case.
Comment #15
jabapyth commentedso all other modules install fine?
--yes the CVS version (and the dev version) are more updated than the latest "stable" version.
Comment #16
naheemsays commentedYes, all others that I have tried do install fine, however, I cannot seem to find the module on a different install when using "Find" (once again using 1.3)
The module is located at http://drupal.org/project/vertical_tabs.
(since the latest dev release was also from the same day, I wrongly assumed they had the same files...)
Comment #17
Antinoo commented@jabapyth: no, it was not giving me that error.
Comment #18
Antinoo commentedjust for your information, my Drupal installation is at /public_html/.
Without the initial '/', I think plugin_manager was trying to create public_html/sites/all/modules/views/.
Since Drupal index.php is at /public_html/, this maybe means that plugin_manager was trying to create /public_html/public_html/sites/all/modules/views/.
And this resulted in an error (suppressed by the use of @ when calling ftp_mkdir()).
Hope this helps.
Giovanni
Comment #19
jabapyth commentedstrange -- that shoudn't have failed..... (even though it was wrong)
Comment #20
ari-meetai commentedI second this. This seems as a good solution.
Comment #21
ozish commentedI am getting this error on a fresh install of Drupal 6.15, using Plugin Manager 6.x-1.10, when I try to install FCKeditor 6.x-1.4.
Happy to help if you let me know what more information you need.
Comment #22
bigsurs commentedI get the exact same error reported by ozish after trying to install the latest update of FCKEditor module.
Cannot install plugin of type
Unable to install fckeditor
Now the plugin manager is pretty much unusable because FCKEditor doesn't show up in the module options, but does show up where I can pick the version. This seems to be a bug. See attached screenshots.