Fotobook reports an upgrade available (from 2.1 to 2.2) but your plugin fails to download the upgrade. However, it does delete the existing plugin! Your error checking should check to see whether the update can be downloaded before deleting the existing plugin.

JAW Popular Posts Widget asks “Would you like to upgrade xxx from version 1.0.1 to version” and doesn’t give me a new version number.

OPML Browser Widget asks to “upgrade” from 1.3.0 to 1.2.1!

Otherwise its great

I do have a few frustrations with it though.

1. When installation of a new plugin is complete, we get message that install was successful, but when you scroll down the new plugin is not displayed. The page needs to refresh before the newly downloaded plugin shows in the Available list. Add a refresh to your code.

2. I know this one is not your fault, but it would be nice if Pluginstaller handled plugins that don’t come in their own subdirectory. Maybe your code could unzip, look for a subdirectory, and if not found … finds the new plugin in the plugin directory and proceeds anyway.

3. Not all new updates found update correctly when I click on the yellow update box.

Overall I am fairly satisfied with Plugin installed and I must say it is one of the few plugins on WordPress that works as described. The one issue I do find with it is this:

If I download a plugin, and then extract it

Then upload it to the correct directory in WordPress

Verify that all files have uploaded correctly

Then go to Plugin installed admin panel to activate it about 30% do not activate. If I try to delete a plugin that does not install plugin manage abot 90% of the time is unable to unistall it.

Another problem that I encounter with plugin manager is if install an update for a plugin in which plugin manager identifies as an upadate as being available. Once the updated plugin has been correctly installed plugin manager does not remove the update notice.

One feature I would like to see in the future is the ability to download a update directly from the admin panel and then have it installed correctly.

The automatic installation of plugins is problematic in that it will blow away the CVS subdirectories.

I would suggest an option to load and keep the plugin zip file in the plugin directory without actually doing the installation. It’s easy enough to do by hand and make sure the CVS gets updated properly: I have to do that by hand anyway for security purposes anyway.

Thanks!

The problem is that file_get_contents gets an 404 and the it blows up on curl_init() because I don’t have that.

Maybe something along the lines of the following would be better

function u_get_contents ( $filename ) {
if ( ! (ini_get(’allow_url_fopen’) && function_exists(’file_get_contents’)) ) {
$curl = curl_init( $filename );
curl_setopt($curl, CURLOPT_HEADER, FALSE); // ignore any headers
curl_setopt($curl, CURLOPT_RETURNTRANSFER, TRUE); // return result
curl_setopt($curl, CURLOPT_FAILONERROR, TRUE); // fail on http-errors
$response = curl_exec($curl); // get the file
$errno = curl_errno($curl);
curl_close($curl);
if ($errno == 0)
return $response;
else
return FALSE;
}
else {
return file_get_contents ( $filename );
}
}

Anyway, even with this change it still doesn’t work.

1. First it blows up on akismet which doesn’t have a readme.txt.
2. And for the rest of the plug-ins it seems $plugin_svn is set to nothing.

I could probably get around 2 by just uninstalling them and let your plug-in install them instead. But even with this workaround you really should implement more error reporting. If I understand the code correctly it would just silently ignore 1 and just report that there is no updates.

If readme.txt is missing, I guess you could search for the “Version:” tag in the php files and compare to the installed version.

if you can repair it in a update is a great thing

the problem is
when i uncheck the discussion options or i toggle the discussion option from the wp script the plugin installer don’t work
it give me a lot of error

kisses