FireStats wurde nicht in die Datenbank installiert

PlugInstaller WP plugin

Current Version: 0.2.1

Are you using PlugInstaller? Please take this 2-minute survey about PlugInstaller!
Or you may want to consider donating to support the development of new features!
And if you miss a feature or functionality in the current version, post your feature wishes here!

If you don’t know which plugins you might try out, look at the plugin reviews page!

Table of Contents

  1. Description
  2. Download
  3. Installation
  4. Uninstallation
  5. Changelog
  6. Wishlist
  7. Donate

About PlugInstaller

PlugInstaller is a WordPress plugin-management plugin that eliminates the need to download a plugin archive, upload it to your FTP server and unpack it manually. With PlugInstaller, you can easily enter a plugin URL (e.g. directly from a plugin repository website like the plugin repository) within the admin interface which is in turn automatically downloaded and installed on your server or you can upload a file from your local file system which is also automatically installed. If you do no longer like one or more plugins that you previously installed, you can uninstall those plugins with a single click.

Additionally, PlugInstaller features automatic update checking and automatic update installation for plugins that are hosted and downloaded from the plugin repository.

PlugInstaller 0.1.9 Screenshot

With PlugInstaller you will no longer have to use any other software than your WordPress administration interface to install or uninstall plugins. In addition to that, plugin installation will hardly last more than 5 to 10 seconds with PlugInstaller, as there is no user interference required. You can also display the readme file provided along with any installed plugins with a single click from your plugin management page.

PlugInstaller now also supports the installation of non-standard directory plugin packages (e.g. where the actual plugin is contained in a subdirectory of the main plugin directory). Additionally, if that should fail, there is an option to discover and delete “broken” plugin installations.


Download (Linux/UNIX OS only!): (12.80 KB) (from the wordpress plugin repository)



Make sure your server has the following tools installed and readily available within the search path: “tar”, “gzip” and “unzip”. Also, set your wp-content/plugins directory to world-writeable (chmod -R 777 plugins) or at least writeable to your httpd user.


  1. Upload the plugin package to your wp-content/plugins directory
  2. Unzip the package (unzip
  3. Go to your “plugins” administration page and activate the PlugInstaller plugin
  4. Read the instructions provided on the “Plugins/Install” page and inside the readme.txt file.

Note: For wordpress installations on windows servers, I recommend the OneClick installer plugin by Anirudh Sanjeev (project page and download), it’s currently not as powerful as PlugInstaller, but should work on windows machines, too.


If you don’t like PlugInstaller anymore, you can easily uninstall it. However, you should not use PlugInstaller to uninstall itself, but delete the PlugInstaller directory manually, in your FTP client.

If you have uninstalled PlugInstaller, you might be confronted with “stuck” or “locked” plugin directories you cannot delete in your ftp client. The reason for this behavior is, that any plugins that were installed using PlugInstaller don’t belong to the user you are using to FTP into your installation, but belong to your webserver’s user (usually www-data, httpd or apache). Don’t worry, there is an easy way to fix this. If you have root access to your server, you might run a chmod -R 777 *  inside your plugin directory. If you don’t have root access (or if you don’t even know what “root access” means), please proceed as follows:

  1. Download the file ““.
  2. Install it using PlugInstaller or unzip it and upload it to your plugins directory.
  3. With your webbrowser, go to “”
  4. If you get a message saying “/path/to/your/wordpress/plugin/directory and all subdirectories have been unlocked”, you may delete the desired plugins.
  5. I strongly recommend you delete the unlock.php file from your plugins directory, as it may open a possible security leak.


New Features (0.2.1)

  • Fixed a severe bug that could lead to complete unusability of all your installed plugins
  • Fixed a minor issue with the uninstallation confirm message box

New Features (0.2.0)

  • Enhanced the update mechanism (will now work with almost all hosted plugins)
  • Support to install non-standard plugin packages
  • Support to discover and remove broken plugin installations

New Feature (0.1.95)

  • Fixed two bugs regarding warning messages on the plugin management page and for non-standard-directory wp installations.

New Features (0.1.9)

  • completely redesigned and cleaned up plugins management page
  • install and uninstall plugins directly from the plugins management page
  • check for updates for hosted plugins (see FAQ section in the readme file)
  • bug fixes for people with a non-standard directory installation of wordpress
  • Important information for upgraders: The installation/uninstallation feature is no longer found on a separate admin page but within the main plugin management page!

New Feature (0.1.7)

  • cURL fallback for people without fopen_wrappers (fixed from 0.1.6, thanks to angrycamel)

New Features (0.1.5)

  • automatic uninstallation of plugins
  • display readme file after installation
  • display readme files for already installed plugins
  • guess file type when downloading from a redirect page (does not work with


Planned features:

  • Browse the repository from your admin interface and directly install plugins with a single click (0.2.x)
  • i18n (0.2.x)
  • “Activate all” button for disabled plugins (0.2.x)
  • Support for the repository (0.2.x)
  • Ability to self-update PlugInstaller (0.2.x)

Do you still miss a feature? Post your feature request here!

Problems or comments?

Just write a comment below!

108 Antworten auf “PlugInstaller WP plugin”

1. von fiLi's tech UNITED STATES am 23.05.2007 um 02:30 Uhr

Top methods for keeping your Wordpress installation and Wordpress plugins up-to-date…

Keeping your Wordpress installation and plugins updated is an important yet annoying task. Following and the news on Wordpress releases, monitoring the versions for the dozens of  plugins installed, and then going through the upgrade can be v…

2. von Tim Norris am 18.06.2007 um 14:08 Uhr

Amazing plugin, thanks!

3. von Graeme UNITED KINGDOM am 26.06.2007 um 17:00 Uhr

Every time I activate this plugin, in the main WP plugins page I lose the “Deactivate all” button at the bottom. Running version 2.2.1 of WP and 0.1.7 of your plugin.

Any ideas?

4. von Henning GERMANY am 26.06.2007 um 17:06 Uhr

Oh, I did not notice they added this link in 2.2 - As I have to change some things within the standard Plugins page, I am completely replacing the default Plugins page with another one provided by this plugin.

Currently, the only solution to this is, if you want to deactivate all plugins, to disable PlugInstaller and then click the disable all link.

Thanks for the hint, I will include that link in the next release.

5. von Ben am 28.06.2007 um 22:26 Uhr

0.1.9 looks good on an installation on the root web directory.
It has two problems.
1. The Google (XML) Sitemaps v.3.0b7, the plugin tells me that I need to upgrade to 2.7.1 which is actually a downgrade. Is there an ignore this plugin for update checks option?

2. My second problem is that it no longer works at all on a wp installation that is in a subdirectory for me. The plugin activates but nothing shows at all now like it does for a web root based installation.

6. von ovizii GERMANY am 29.06.2007 um 12:56 Uhr

some suggestions:

you could ajaxify the tabs so I can drag my inactive plugins up, and maybe a +/- symbol would be great so I can close the tab with active plugins and concentrate on the inactive plugins list?

otherwise its looking great although the check for plugin updates takes very,very long…

oh and it makes another nice plugin useless and unuseble:

maybe you could incorporate its features?

and this plugins features would also work well with your plugin:

7. von Henning GERMANY am 29.06.2007 um 13:04 Uhr

Well, the drag & drop feature has been on my wish list, as well as the “+/-” links that I tried to enable, but failed due to some not identifiable problem with the dbx extension. If somebody could help me on dbx boxes, I will include the +/- links as soon as possible.

I will take a look at the two plugins you suggested and then decide which of their features i might include in my own plugin.

Sorry, the checking for updates heavily relies on the speed of the svn repository which turns out to be slow at times. Until there is a centralized version information server als suggested by some of the users, this is a problem we have to live with, i suppose.

8. von ovizii GERMANY am 29.06.2007 um 13:07 Uhr

the update was slow but works great. could the updated plugins be automatically be reactivated if they were activated before?

also I get an error after each action I make in your plugin, like activate/deactivate, update, etc. (using firefox 2.??)

it says: window.onload: TypeError table has no properties - undefined

9. von Henning GERMANY am 29.06.2007 um 13:26 Uhr

ovizii, akismet really doesn’t like you ;)

Initially, I wanted to have plugins automatically automatically being reactivated after update, but that failed for the simple reason that the updated plugin (resp. the older version of it) is still loaded into wordpress at the time the update is performed. So if I try to reactivate it after updating, php throws lots of “cannot be redeclared” errors. The only solution would be to automatically re-load the management page after the update has been performed, and then automatically activate it. I will consider this.

Which Firefox are you using? For me, it works fine and without javascript errors on

10. von Kommie FINLAND am 03.07.2007 um 21:40 Uhr

I Tried to install your plugin, but when i activate it, it gives an “internal server error” (error 500 maybe) I have the plugins folder chmoded 777 but im not shure how available I have the tar gzip and unzip. Could it be the problem. I’m running wp 2.2 on my server. After the error i’m not able to return to the plugins page as it gives the same error every time. I have to delete the pluginstaller folder by ftp to remove the error. please help.

11. von Henning GERMANY am 03.07.2007 um 21:47 Uhr

This is very strange… 500 errors usually only occur with misconfigured server configuration files (like the .htaccess file). The plugin itself does not do much more than exchanging the plugins.php file. Do you get this error on every admin page or just on the plugins page? And did you try to install an older version of PlugInstaller (go to and select an older version)? Does that work? The availability of tar and so forth is quite surely not causing this problem. But you might run into problems if neither fopen_wrappers nor cURL are installed on your server (I don’t know what kind of error this would give, but it may well be an 500 error).

12. von Tyson UNITED STATES am 04.07.2007 um 02:58 Uhr

Seems to be working well now thanks!

has a problem unpacking all-in-one-seo for an update but I deleted the old version and it works manually.

13. von Andrew UNITED STATES am 04.07.2007 um 07:05 Uhr

I love this plugin. It’s really great now that the old plugin installer that worked with doesn’t seem to work anymore. You should really think about making a theme installer too.

14. von ovizii GERMANY am 04.07.2007 um 09:13 Uhr

one more suggestion: I found the button: deactivate all from your plugin, see this extended functionality:

and what about extending your plugin to also support diferent formats, like the old plugin did? i.e. .txt .php files? At the moment I have to download those single-file plugins, zip them and upload them again :-)

15. von martin SWEDEN am 04.07.2007 um 21:56 Uhr

On one server I’m stuck with wordpress 1.5 because of MySQL 3.xx. Is your great plugin only available for WP 2.xx?

- martin

16. von Henning GERMANY am 04.07.2007 um 22:00 Uhr

Well, you could try to install it under 1.5, it can do no harm to your installation, if the plugin directory etc. is the same (i.e. /wp-content/plugins). If you are successful, please notify me so I can update the version information.

Viel Glück!

17. von Alberto SPAIN am 05.07.2007 um 10:54 Uhr


I’ve just installed the plugin but the standar plugin admin page is still there. I’m running a brand new installation of Wordpress 2.0.9. What’s the problem?

18. von ovizii GERMANY am 05.07.2007 um 13:50 Uhr


wp 2.2.1 your plugin 0.2.0

I just had a BIG problem happening: I downloaded slugtrimmer.php, zipped it up so I can install it with your installer - after installing I had a lot of akismet errors (although it was not activated, and then all of a sudden half of my plugins disappeared.
I don’t know - I guess it was the installers fault: all plugins were moved a directory deeper into the akismet directory… I just moved them all out again and its working again.
I didn’t make a screenshot, so this is all I can tell you…
btw. inside wp-content/plugins/ there was only the akismet folder and below it another akismet folder and so on,… I did maybe 5 cd akismets but got tired of it and deleted the folder. wp-cotnent/plugins also contained another akismet.php-upload file or similar, I can’t really remember it…

I hope this helps find the problem…

19. von Henning GERMANY am 05.07.2007 um 14:19 Uhr

ovizii: I think you didn’t include a subdirectory inside your zip file. This is currently unsupported (as I just forgot to test for this issue). I will try to fix this as soon as possible.

Alberto: Did you put your wordpress installation into your website’s main folder or into a subdirectory?

20. von ovizii GERMANY am 05.07.2007 um 14:35 Uhr

indeed I did not include a subdirectory. but I have been using your plugin since you started it, and I never included a subdirectory :-?

my structure looks like this: /var/www/webXX/web/wp-content/plugins so wp is installed directly into the root without subdirectory.

21. von Henning GERMANY am 05.07.2007 um 14:37 Uhr

Alberto: Why are you installing a “brand new” wordpress using 2.0.9 while 2.2.1 is the current version? I have not yet been able to verify pluginstaller 0.2 on anything less than 0.2, but you might succeed by downloading and installing version 0.1.6 which can be still found at the plugin repository (select “other versions”). I will try to perform a test installation of 2.0.9 to check the plugin with that.

22. von Henning GERMANY am 05.07.2007 um 14:39 Uhr

ovizii: yep, but 0.2 includes a mechanism to automatically resolve directory problems (which occur, for example, if someone provides his plugin in a nested directory structure like the wp-polls or wp-stats plugin). I forgot to omit those checks if a plugin is directly installed into the root directory. Will be fixed immediately.

23. von ovizii GERMANY am 05.07.2007 um 15:06 Uhr

download of gives 404 error

24. von Henning GERMANY am 05.07.2007 um 15:08 Uhr

The issue ovizii described in his post is fixed in version 0.2.1 of PlugInstaller that has just been released. I urge all users of 0.2.0 to immediately upgrade their installation to prevent major damage to their wordpress installations.

25. von vijay INDIA am 05.07.2007 um 15:28 Uhr

oops, i tried to upgrade to version 0.2.1 and got message that problem occurred during the unpacking..
What could be the reason?

Instead of clicking upgrade button, can i deactivate and reinstall the plugin? will my currently installed other plugins will have any effect by this?

26. von Henning GERMANY am 05.07.2007 um 15:38 Uhr

ovizii: not any longer, but to prevent other people from downloading the corrupt version, I changed the download link even before it has actually been available on You can now download the updates.

vijay: Actually, PlugInstaller is unable to upgrade itself (see the readme file for an explanation), but you can always delete it and install the new version by hand. Maybe I can discover a method to make PlugInstaller be able to upgrade itself, if anyone has suggestions, let me hear them :)

27. von tash UNITED STATES am 05.07.2007 um 19:07 Uhr

If you want a way to have pluginstaller upgrade itself, you could do this :
Have PlugInstaller download and activate a temporary plugin which
disables the current pluginstaller
downloads/unpacks the new one
activates it
And then have PlugInstaller delete that temporary plugin. It seems like it’d be a good enough solution to me to have it update without any problems.

28. von BenjieP UNITED STATES am 08.07.2007 um 18:30 Uhr

I like it! I had been thinking this would be a great plugin to do, except I don’t know php yet. Thanks!

29. von GERMANY am 09.07.2007 um 18:12 Uhr

Blogistan Panoptikum Woche 27 2k7…

iPhones und der gestrenge Herr Google dominierten der Tech-Berichterstattung der Woche. Außerdem gibt’s einige WordPress News und ein Update der teuersten Domains aller Zeiten.

30. von Tyson UNITED STATES am 10.07.2007 um 03:19 Uhr

What is the added security risk of having unlock.php in the plugins folder, doesn’t pluginstaller need that whole folder at 777 anyway?

31. von Henning GERMANY am 10.07.2007 um 07:29 Uhr

I don’t know if there is an immediate security risk, but as the downloadable unlock script could chmod every directory (the correct directory is determined by the script file location), this might be a possible risk if someone can crack php’s $_SERVER superglobal. I think this is quite improbable, but why should we “play with the fire” :)

32. von kerry UNITED STATES am 10.07.2007 um 15:05 Uhr

I installed and activated pluginstaller in my wordpress 2.0 plugin directoy but i dont get the screenshot above, instead its the same as before and i can not so anything with it. Please help.

33. von ovidiu ROMANIA am 12.07.2007 um 00:16 Uhr

found another problem. I tried activating upload+ plugin and nothing happened. it just got not activated.
then I deactivated your plugin, tried again and got this error: Plugin could not be activated because it triggered a fatal error.

can you modify your plugin to show these errors too?

34. von Tomsn AUSTRIA am 14.07.2007 um 10:37 Uhr

HI, i installed your latest Plugin 0.2.1 but on my Admin - Plugin’s Page i get the message: A newer version of PlugInstaller is available! Update… on every click i do … is this normal? is there a newer Pluginversion?

35. von andrabr UNITED STATES am 15.07.2007 um 22:30 Uhr

It would seem I have found a bug (or a feature?) in version 0.2.1:

in pluginst.php you have a line:
include(ABSPATH. PLUGINDIR .’/pluginstaller/plugins.php’);

However, in Wordpress 2.0 PLUGINDIR is not defined (things may be different in 2.1, 2.2 or MU - so it may be a feature, not a bug).

The solution is to add one line, so that the last three lines of the file look like this:

define (’PLUGINDIR’, ‘wp-content/plugins/’);
add_action(’admin_notices’, ‘pi_replace_plugins_page’);

Oh, and the plugin names come up centered, not left adjusted - by design? (I have no problem with that).


36. von andrabr UNITED STATES am 16.07.2007 um 06:11 Uhr

maybe it’s a feature or maybe it’s a bug, but “uninstall” option was not working for me until I added “/wordpress” into the following line:

$uninstall = ““.__(’Uninstall’).”“;

- the path was missing it and so uninstallation was not happening.

37. von Henning GERMANY am 16.07.2007 um 16:53 Uhr

Sorry for the late reply, but I’ve been on vacation the last five days.

If you don’t get the screenshot shown above, the replacement routine for the plugins.php admin page has somehow failed. This might happen if you did not install PlugInstaller into the default directory (but it worked for me on my test blog, that is not installed inside the default directory). Another reason might be that you are using an outdated version of wordpress (e.g. < 2.2), you should check this.

An outdated version of Wordpress is also the reason why the PLUGINDIR constant is not defined. As of WP 2.2, this constant is set to your plugin’s directory, relative to the wordpress installation path. I will try to check the definition of the constant in the next release and set it if it is not set, so you will also be able to use PlugInstaller with any 2.x Wordpress version.

The problem with PlugInstaller showing that an update is available might be caused by incompatible php settings. Did you experience problems on downloading plugins directly from the web, too?

38. von andrabr UNITED STATES am 16.07.2007 um 21:00 Uhr


I have the problem with PLUGINDIR because I am stuck with WP 2.0 - a key plugin has not been upgraded to work with 2.2
I still love Pluginstaller - since the change above it works like a charm!

39. von suzanne UNITED STATES am 27.07.2007 um 00:10 Uhr

I had a problem installing the pluginstaller and this is the error message I got:

Warning: main(/home/content/f/r/e/freelancedaily/html/freelance-writing-scams/wp-content/plugins/pluginstaller/ui.php): failed to open stream: No such file or directory in /home/content/f/r/e/freelancedaily/html/freelance-writing-scams/wp-content/plugins/plugins.php on line 4

Fatal error: main(): Failed opening required ‘/home/content/f/r/e/freelancedaily/html/freelance-writing-scams/wp-content/plugins/pluginstaller/ui.php’ (include_path=’.:/usr/local/lib/php’) in /home/content/f/r/e/freelancedaily/html/freelance-writing-scams/wp-content/plugins/plugins.php on line 4

I would really really appreciate any help you can give me ;) Thanks! Suzanne

40. von z-division LITHUANIA am 27.07.2007 um 08:40 Uhr

after installing from file or url message is:
“Your plugin has been successfully installed. Please view the plugin’s readme file before activating it!”

any of the new plugins displayed in active or not active directories.
the above message says :

Warning: exec() has been disabled for security reasons in /home/…/domains/ on line 96

chm for wp-content/plugins is 777

any suggestions?

41. von z-division LITHUANIA am 27.07.2007 um 09:19 Uhr

btw same thing happens after updating plugin error line says:

Warning: exec() has been disabled for security reasons in /home/…/domains/ on line 96

42. von Henning GERMANY am 27.07.2007 um 10:37 Uhr

Suzanne: There seems to be something wrong with your installation of pluginstaller. You seem to have installed into your root plugin directory (/wp-content/plugins) instead of /wp-content/plugins/pluginstaller. Try removing all the files from the pluginstaller archive from this folder and extract or upload the whole pluginstaller zip file into the /wp-content/plugins folder, this should create a folder /pluginstaller with all the needed files inside.

z-division: I’m afraid your webhoster does not allow php to execute system commands. As pluginstaller heavily relies on the gnu tools (tar, gzip and unzip) to handle downloaded archives, it fails on your system. You might want to take a look at the OneClick plugin (see the link in the description, at “installation”) which uses a php library to unpack plugin files and does not need the rights to use commandline tools.

43. von z-division LITHUANIA am 27.07.2007 um 10:48 Uhr

von Henning:
- you were right - webhoster. oneclick works properly. thanks again.

44. von Ngadutrafik 2007 INDONESIA am 28.07.2007 um 04:24 Uhr

It’s seem good plugin, i will try it.

45. von suzanne UNITED STATES am 28.07.2007 um 17:19 Uhr

OK … what you told me to do worked … I thought! It was there listed in my plugins and when I hit “Activate” it took me to this:

Warning: pi_replace_plugins_page(/home/content/f/r/e/freelancedaily/html/freelance-writing-scams/wp-content/plugins/pluginstaller/plugins.php): failed to open stream: No such file or directory in /home/content/f/r/e/freelancedaily/html/freelance-writing-scams/wp-content/plugins/PlugInstaller/pluginst.php on line 31

Warning: pi_replace_plugins_page(): Failed opening ‘/home/content/f/r/e/freelancedaily/html/freelance-writing-scams/wp-content/plugins/pluginstaller/plugins.php’ for inclusion (include_path=’.:/usr/local/lib/php’) in /home/content/f/r/e/freelancedaily/html/freelance-writing-scams/wp-content/plugins/PlugInstaller/pluginst.php on line 31

I’m sorry I don’t know what I’m doing! I really want to get this working as I want to put it on several blogs ;) Thanks again for your help! It means the world to me! Suzanne

46. von Henning GERMANY am 28.07.2007 um 19:04 Uhr

You need to call the folder to put PlugInstaller into “pluginstaller” (note that this is character sensitive, so “PlugInstaller” is not equal to “pluginstaller”. Try to rename that folder into all lower-case letters and it should work.

47. von Tyson UNITED STATES am 06.08.2007 um 08:59 Uhr

Whenever I seem to automatically update all-in-one-SEO-Pack it fails, then when I do it manually and refresh pluginstaller, Akismet shows as deactivated when it wasn’t before…

48. von jon CANADA am 20.08.2007 um 20:16 Uhr

Hi, great plugin.

With this install:

it is breaking. It looks like the internal file structure is not getting created properly when the extraction is done on the server.

49. von Kevin UNITED STATES am 29.08.2007 um 14:33 Uhr

This is a great plugin.
I am in the process of shifting my site to wordpress. Your plugin has been a great help.

I am having one problem. When installing it installs with a user of www-data and a group of www-data which are not the user and group for my test site. Tis is cousing me some minor problems. Is there any way to change the default user and group to match the true user and group for this site.

Thanks for the plugin, time and help.

50. von Henning GERMANY am 30.08.2007 um 22:41 Uhr

jon: Sorry for the late reply, but I’ve been busy in the last few days. I think this is the same problem another person observed, I’ll take a look at this.

Kevin: www-data/www-data is the default apache (webserver) user/group on debian systems, I think. Every file that is written by php (invoked from apache) to the filesystem will get that user and group ownership. There is no way to work around this (and the reason why you should chmod your plugins directory to 777), because you are logging in via FTP or SSH, which is a completely different thing. There is only one server (or at least several instances of the same server) running on the whole server, no matter how many “sites” (virtual hosts) there are on that server. And this server is always using the www-data username. For example, on this server where my blog is installed, the webserver also uses www-data, while I log in with a completely different username (I don’t think that it’s possible to log in as the www-data user).

51. von Henning GERMANY am 30.08.2007 um 22:43 Uhr

By the way… I promised to publish an upgrade already 10 days ago, but as the wordpress authors announced the beta stage for wp 2.3, I’ll wait until 2.3 is released and try to get pluginstaller to work with that, too.

52. von ovidiu ROMANIA am 31.08.2007 um 01:14 Uhr

regarding the www-data issue, there is another option which I successfully use:

try to do a chown -R your_user_login:www-data your_public_html_folder followed by a chmod -R 775 your_public_hmtl_folder

this sets your user as owner and the www-data as owning group, then allows you and www-data to write which allows this plugin to work as the www-data is the owning group, still you can also write as yo uare the owner :-)

this works.

53. von Michael SWEDEN am 31.08.2007 um 14:58 Uhr

Hi, just found out about your nifty little plugin and while i think that its a good and nice looking plugin i got one little problem. When trying to update the “All in One SEO Pack” from withing your plugin, i get the following error:
“A problem has occured while unpacking your plugin package! During the upgrade process, your plugin has been deactivated. Be sure to re-activate it!”, however, if i try to install a new plgin that i have downloaded to my local computer i get this nice message: “Your plugin has been successfully installed. Please view the plugin’s readme file before activating it!”, and i get the same message if i try do install a plugin via an url. Is there a way for you to add some debug or logging capabilities so we can help you figure out what the problem is?

54. von Jon Symons CANADA am 02.09.2007 um 17:48 Uhr

Hi, I didn’t see a repsonse to this problem so I thought I would restate it since I just encountered it again:
“My second problem is that it no longer works at all on a wp installation that is in a subdirectory for me. The plugin activates but nothing shows at all now like it does for a web root based installation.”
When WP is in the “blog” folder, your plugin won’t activate.

55. von alice in wire ITALY am 10.09.2007 um 09:33 Uhr

when i installa a plugin with plugin installer
it copy in my directory all the file in the same server in the plugin directory

56. von Dave UNITED STATES am 11.09.2007 um 02:38 Uhr

This is one of my favorite plugins. It works perfectly, and it’s the first plugin I install on new WordPress blogs!

57. von Brian am 11.09.2007 um 22:56 Uhr

Hello Henning - very cool plugin - have been using it for some time - a small suggestion: after the user has clicked the ‘check for updated plugins’ and the list of plugins with updates is returned, could you also list the plugins that were not able to be checked (probably because they don’t have an entry in the plugin database you’re using to check) - i love clicking the check for updates button and always update my plugins but that left me thinking that I was all up to date - when I went through all my plugins, visiting their homepages, to see exactly what they were doing to see if I wanted to get rid of any, I found that a number of them were out of date because your plugin didn’t know where to check for new versions when they weren’t in the plugin database - I guess the best thing would be for a new line of meta data to be added to the plugin definition - update url - so that plugins like yours could query different sources when checking for updates - but since that isn’t the case, I think just listing the ones that could not be checked would be a good solution for now

Keep up the good work and thanks

58. von floogy GERMANY am 27.09.2007 um 20:09 Uhr

Hi, Thank you for your plugin. I got a big problem, and I suggest, that you’ll test the files before let them begin the installation process.

Like others (e.g. ovizli) before I ran into the problem, that some plugins like “edit n place” and the wrong version (for wp 1.5, my fault) of “tag warrior” began moving every file up from the servers root-directory into the $WP/wp-content/plugin directory!!!
Due to permission Problems this works only for files with writing permissions to the apache-user (e.g. www-data). This moved my gallery2 installation and some websites into the plugin folder! Because I didn’t realized whatz happened, I lost some image-cache files, and had to rebuild the gallery2-cache. Thanks god, I had a backup of an important website.
The document root of these moved websites was in a users home directory.

Please,please,please test the zip, tgz, php and whatever-files, before initiate the installation process.

Thank you for your great plugin, but please let the plugin test the files, before execute them.

59. von floogy GERMANY am 27.09.2007 um 20:12 Uhr

Sorry, I forgot to mention, that this bug appears in wpmu 1.2.5 with your latest plugin-installer Version: 0.2.1 .

60. von Nathaniel UNITED STATES am 03.10.2007 um 22:05 Uhr

I’m having an odd little bug in wordpress 2.3
Strangely, after uploading a new plugin it says that it didn’t install properly or there where problems. The plugin shows up in the “broken” section. However, after reloading the plugins page, it is fine, it activates fine, and generally behaves itself like it should. I think there must be some strange interaction between the pluginstaller and wordpress 2.3 that causing this. It might be worth looking into. It isn’t causing any real problems other than adding a click onto my plugin installation.

61. von Typer Tappers UNITED KINGDOM am 18.10.2007 um 14:16 Uhr

I’m having some trouble updating my files, I have tried changing the plugins directory to 777 but still doesnt work
currently using wp 2.3.

62. von Dan UNITED KINGDOM am 20.10.2007 um 20:20 Uhr

Great Plugin. Am though having same problem as others on both Unix and Linux server installations of WP 2.3. Folder /wp-content/plugins/ is set to ‘777′ and installing a new plugin works a treat, but can’t seem to upgrade anything, as get error:
“A problem has occured while unpacking your plugin…”
Probably something to do with the way permissions for files/folders are being written by the app, but not sure now to fix. Any help greatly appreciated.

63. von ovidiu ROMANIA am 29.10.2007 um 13:26 Uhr

could this plugin be made compatible with the wp 2.3.1 “css markup” so we can also see if there is an update reported by wp 2.3.1 or is this plugin checking the same plugin database and reporting the same upgrades?

if so, it is better than the integrated wp 2.3.1 update check as it also offers upgrading not only notification.

64. von ovidiu GERMANY am 13.11.2007 um 12:20 Uhr

getting this error:

addLoadEvent(loadMenus); function loadMenus() { var xMenu = document.getElementById(”adminmenu”); xMenu.innerHTML=”"; var newDiv = document.createElement(”div”); newDiv.innerHTML = ”

after clicking the check for updated plugins button, using your plugin 0.2.1 and wp 2.2.3 any ideas?

65. von Tim UNITED KINGDOM am 23.11.2007 um 03:30 Uhr

Thanks for this really useful plugin! It is so handy to use at work when I am behind a company proxy that denies me the ability to use FTP or upload anything at all.. your plugin lets me sneak past that problem :P Cheers :)

66. von Belen SPAIN am 23.11.2007 um 15:42 Uhr

Hi, I have been updating to wordpress 2.3.1 and I’ve just installed the plugin but the standar plugin admin page is still there. I made a new web last week with wordpress and it worked the plugin at the same server, so I have just copied the other web, changed the name and changed the wp-config to access to sql files correctly and it doesn’t work the plugin.
What can I do?

67. von Cecilia Tan UNITED STATES am 03.12.2007 um 11:36 Uhr

Hm. I’m running WP 2.0.4 (which should work, no?) and the only thing I can think of that I did differently in my install is that I downloaded the Pluginstaller zip to my desktop machine first, unzipped it there, and then used SCP (my admin won’t let us use FTP) to upload the pluginstaller directory into the /wp-content/plugins/ directory.

Does it matter if the unzipping happens first before the upload? Most every other plugin I do this way.

Anyway, the problem is when I chose “Activate” the Plugins page in my wp admin window goes completely blank. Somehow the plugins.php replacement is breaking it, but I can’t diagnose how. Nor can I deactivate it, since the page is blank. Deleting the whole pluginstaller directory seems to be my only choice.

68. von Nate am 04.12.2007 um 01:02 Uhr

I am having the same problem as von Belen (#66).

I have a fresh install of WordPress 2.3.1. I then copied PlugInstaller to my /wp-content/plugins/ directory. Went to the Plugins page (/wp-admin/plugins.php), and PlutInstaller 0.2.1 shows up in the list as expected. Clicked “Activate” and got the message “Plugin activated” and the PlugInstaller row now shows up in green. But it’s still the old Plugin Management page. It appears to think PlugInstaller is installed and activated, but obviously isn’t using it.

Any ideas?

69. von jessie PHILIPPINES am 18.12.2007 um 17:57 Uhr

i might as well give this a try… at the moment, i’m having a problem with the default admin section of wordpress

70. von Andy BRAZIL am 19.12.2007 um 20:00 Uhr

Oh, and did not know about it. Thanks for the information …

71. von Jonathan UNITED STATES am 20.12.2007 um 00:17 Uhr

I’m having the same problem as Nate #68.

I’m downloading the zipped plugin file, unzipping it and then uploading via FTP to my server. I then go to the plug-in page to activate the plugin activate it, but the new plug-in page does not appear. Please help.

72. von The Review Blog INDIA am 20.12.2007 um 20:29 Uhr

Nice Plugin , Working with me . I have WP 2.2.1 and it works fine with this Wordpress Version. Will try with 2.3.1 as well and then let you all know.

73. von Blog Opinion INDIA am 24.12.2007 um 12:07 Uhr

Nice plugin and concept to manage your plugin easily.

74. von evden eve TURKEY am 25.12.2007 um 18:10 Uhr

thx for your cdng this plugin

75. von ts UNITED STATES am 25.12.2007 um 19:26 Uhr

While trying to install a plugin with this plugin - Fatal error: Call to undefined function curl_init() in /var/www/wp-content/plugins/pluginstaller/utils.php on line 27

76. von bbbco UNITED STATES am 28.12.2007 um 07:36 Uhr

I keep getting an error when I activate a new plugin.

“Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 184320 bytes) in /home…/wp-content/plugins/pluginstaller/plugins.php on line 313″

Also, I get the deactivation error when trying to update (Akismet) as well.

I am using the latest updates of both WP (2.3.1) and your plugin (0.2.1). Thanks!

77. von Craiger am 31.12.2007 um 18:49 Uhr

I’ve installed latest version on a new blog, but every time I try to install a plugin from the Enter URL method it is not working.

It displays:
An error has occured
A problem has occured while trying to download your file!

Go back and try again

I’ve tried it with 5 different plugins that I know it has uploaded correctly on some of my other blogs.

Also, other problem … 0.2.1 — Keeps telling me there is a new version of PlugInstaller even though I just installed the latest version on a new blog.

Is there any issue of using this on a webhost that does not use cPanel?


78. von sanghala INDIA am 02.01.2008 um 13:21 Uhr

I am getting the following error when i tried to update the plug-ins.

Fatal error: Call to undefined function curl_init() in /var/www/virtual/ on line 27

Please reply back…!

Thanks in Advance..

79. von suzanne UNITED STATES am 06.01.2008 um 17:38 Uhr

Hi … I have installed this great plugin before … and I’m trying to put it on a new blog of mine and I get this error:

Warning: pi_replace_plugins_page(/hsphere/local/home/suzannef/ failed to open stream: No such file or directory in /hsphere/local/home/suzannef/ on line 31

Warning: pi_replace_plugins_page(/hsphere/local/home/suzannef/ failed to open stream: No such file or directory in /hsphere/local/home/suzannef/ on line 31

Warning: pi_replace_plugins_page(): Failed opening ‘/hsphere/local/home/suzannef/’ for inclusion (include_path=’.:/usr/local/share/pear’) in /hsphere/local/home/suzannef/ on line 31

Any idea what I did wrong?

Thanks for the help ;) Suzanne

80. von Jabl[x]o SLOVAKIA am 08.01.2008 um 00:15 Uhr

just a little quick-fix. After some error warning (…utils.php on line 42) /funny that particulary this one/ i’ve modified utils.php:

$fp = uopen(’’,'r’);
$available_version = fgets($fp);

if($fp = uopen(’’,'r’))
$available_version = fgets($fp);

On localhost it gives no update notification, on internet it does. I didn’t investigated any further, though.

I like the idea of this plugin anyway :)

81. von froesch GERMANY am 11.01.2008 um 17:56 Uhr

Pluginstaller is cool but the uninstallation of other plugins does not work.

WP 2.3.2 DE-Edition
Pluginstaller 0.2.1

Not Found
The requested URL /wp-admin/plugins.php was not found on this server.
Apache/2.2.3 (Debian) mod_ssl/2.2.3 OpenSSL/0.9.8c Server at Port 80 would be the right adress.
any idea? seems to be just a configuration problem

82. von Manguilio VANUATU am 15.01.2008 um 00:18 Uhr

I am absolutely lost. I tried pluginstaller today, the last version. I do not have anymore any plugin and I can’t access it. I do not find anymore too the pluginstaler directory n the plugin directory and I have the following warning message. If somebody can help thanks

Warning: main(/home/connect/public_html/jonalam/wp-content/plugins/pluginstaller/ui.php) [function.main]: failed to open stream: No such file or directory in /home/connect/public_html/jonalam/wp-content/plugins/plugins.php on line 4

Fatal error: main() [function.require]: Failed opening required ‘/home/connect/public_html/jonalam/wp-content/plugins/pluginstaller/ui.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/connect/public_html/jonalam/wp-content/plugins/plugins.php on line 4

83. von Nikolay RUSSIAN FEDERATION am 26.01.2008 um 02:19 Uhr

;( Work only old ver.

84. von jps61974 PHILIPPINES am 12.02.2008 um 09:22 Uhr


i have one blog which i might try installing this plugin. at the moment i’m really having problems with wordpress plugins for making my website load slowly.

85. von Fanna am 26.02.2008 um 23:41 Uhr

This is really great idea. Real plugin-management that eliminates the need to download a plugin archive.

86. von awolf42 GERMANY am 27.02.2008 um 16:32 Uhr

Any other plugin I try to install via PlugInstaller will be listed under “Broken”. Nothing is really installed, not even the plugin’s subdirectory (e.g. trying The plugins directory itself is set to 777. No difference using download from URL or upload from local disk.

A 2nd issue is, trying the “checking for updated plugins” will result in server error 500.

I use WP 2.3.1.

Any idea?

87. von Becky UNITED STATES am 03.03.2008 um 00:58 Uhr

I’ve used this on other blogs, on the same host (GoDaddy) and it worked fine. It was working up until the point I upgraded my WP installation to 2.3.3, at which point the plug ins always showed up as a “Broken Plug In”. I’m not entirely sure why - the entire directory for the plug in was correctly unpacked/uploaded on the server. If I manually upload the plug ins, things work just fine. I haven’t tried this with the plug in repository yet, but I’m guessing I’ll get the same problem. I don’t receive any errors during the upload.

88. von Zabeliski GERMANY am 06.03.2008 um 12:10 Uhr

After Upgrading to WP 2.3.3 the plugin doesnt work anymore. It shows the new versions of the plugins, but nothing gets installled?

89. von Peter am 10.03.2008 um 13:36 Uhr

This plugin is great help to a blogger. I will take your survey now. Glad I could help in development of such wonderful plugin.

90. von chris am 10.03.2008 um 19:23 Uhr

I love this plugin. The only issue I have run into is that if I have a plugin that I want to uninstall, the link does not work. on the rollover, the statusbar at the bottom of my browser says:


any ideas

91. von work at home IRELAND am 14.03.2008 um 22:55 Uhr

I’m using the plugin on a wp 2.3.3 install,
when I try and upgrade a plugin I get the error message
[i]A problem has occurred while unpacking your plugin package! During the upgrade process, your plugin has been deactivated. Be sure to re-activate it![/i]

I chmod the /plugins/ folder 777 but this made no difference

I see other commenters with same issue but no solutions being offered, does it work with wp 2.3+?

Million Dollar Training System

92. von Jan DENMARK am 21.03.2008 um 12:01 Uhr

Says there is a update but no update :(

93. von john AUSTRALIA am 25.03.2008 um 19:05 Uhr

hope it workwith wp 2.3 thank you

94. von Scott Ficek am 28.03.2008 um 16:51 Uhr

I love this tool. I just installed a new WP blog 3.3.2. The first plug-in I always install is this one. It installed correctly, but all the plug-ins I install with the tool initially are listed as broken plugins. When I refresh the page, it then says they installed correctly and in the available by inactive section.

95. von Filmbox GERMANY am 31.03.2008 um 17:11 Uhr

I just deactivated the plugin and run the unlock.php.

Updated with instant upgrade tp WP 2.5 without problem.

Then checked which plugins to updated and set on only these files and folders to 777.

The automatic update for plugins in wordpress 2.5 worked fine.

Thank you

96. von Uwants HONG KONG am 14.05.2008 um 12:15 Uhr

I chmod the /plugins/ folder 777 but this made no difference

97. von Sanja am 20.05.2008 um 14:53 Uhr

This is great relieve because now there is no need to download a plugin archive. Great time saver plugin.

98. von Jusuna am 28.05.2008 um 20:22 Uhr

I’m satisfied with its performance, especially when it helped fast plugin install.

99. von GabonMx MEXICO am 16.06.2008 um 04:39 Uhr

I want to delete some plugins from my plugins folder but i can’t and the unlock.php says “/path/to/your/wordpress/plugin/directory and all subdirectories have been unlocked”, but it’s not truth because when i login on my ftp i still can’t delete it

100. von am 24.06.2008 um 16:02 Uhr

120+ WordPress Plugins…

Running your Wordpress blog can feel like a full-time job sometimes. We have compiled an A-Z list of more than 120 plugins to help you streamline everything you need to do out back.
AJAX-Powered WordPress Plugins
The WordPress blogging platform has tho…

101. von Tomasso Torr am 26.06.2008 um 01:21 Uhr

This is one of several plugins that I upload on any of my new blogs.

102. von Cole JAPAN am 04.07.2008 um 23:06 Uhr

Great tool. Although, since I found it via the WP plugin repository, I wasn’t sure what was going on with the locked directories and it become a little issue. Neither the readme file included or the FAQ at the WP repository touch on that. It would be very helpful!

103. von Pierss am 06.07.2008 um 12:14 Uhr

Great time saver and great blog management tool. Installing plugins in a glitch is something that all blog master needs.

104. von Adriana am 18.07.2008 um 13:31 Uhr

I’m new in blogging, but when I read all these users of your plugin make me become a big shot blogger. I will try it on my first blog.

105. von Pamela am 22.09.2008 um 21:46 Uhr

I have to listen to my older fellow bloggers. They say this plugin is a must, so here I am.

106. von Mikella am 03.11.2008 um 21:02 Uhr

Plugins are the air for the blog. I have tested your plugin some time back, but now I will try again with my new blog.

107. von Dereck am 15.11.2008 um 22:02 Uhr

This is interesting tool and like it seems it’s a great time saver.

108. von Suzana am 03.12.2008 um 19:38 Uhr

If you do no longer like one or more plugins that you previously installed, you can uninstall those plugins with a single click. That’s very fast and might get very handy in hands of a busy blogger.

Eine Antwort verfassen