The InstantUpgrade plugin (legacy version 0.2)

277 comments on “The InstantUpgrade plugin (legacy version 0.2)”

1. Jamie Talbot on March 12, 2007 at 10:55 #

   Just a quick note - you’d be better off calling load_plugin_textdomain() on the init action hook, to guarantee maximum interoperability with localisation plugins. This looks great in concept, will be keen to give it a try.

   Cheers,

   Jamie.

2. Alex Günsche on March 12, 2007 at 11:20 #

   Yes, you’re right, and I remember to have this done in another plugin of mine. I’ll put it on the TODO list for the next release.

   When you give it a try, I’d be glad to hear your opinion.

3. Ben on March 12, 2007 at 14:03 #

   one thing:
   “writable by the webserver”

   a quick and easy explanation HOW i can make sure and HOW i can set the rights could be very helpful for not so geeky ppl like me.

   is it to change the owner to wwwrun? or to chmod 777?

   well, it worked well for me anyway! than you so much for this plugin! 1:made my day, second: will save helluvalot of time for me now!!!elf!!
   thx!

4. Alex Günsche on March 12, 2007 at 14:20 #

   Yes, you need to apply chmod 777 to the named directories and files. (For files, 666 would actually do, but 777 doesn’t hurt in this case, as there are no standalone executables and the mode is instantly changed back by the server anyway.) I’ll add this to the documentation.

5. suleiman on March 12, 2007 at 15:56 #

   It would be awesome if you could get this to work with WPMU!

6. Jott on March 13, 2007 at 10:23 #

   Hallo, sehr schöne Idee, funktioniert prima…
   Ich versuche gerade, das ganze auf die WP DE-Version umzumodeln, reicht es, wenn ich in der upgrade.php den Link verändere?

   $this->download_url_and_path = 'http://counter.wordpress-deutschland.org/dlcount.php?id=static&url=/de-edition/';
$this->wp_package = ($versionToInstall == 'latest') ? 'latest.zip' : 'wordpress-'.$versionToInstall.'.zip';

7. Alex Günsche on March 13, 2007 at 10:58 #

   Wenn Du immer auf die neueste Version aktualisieren willst, sollte das klappen. (Du kannst es ruhig ausprobieren; sollte der Downloadversuch Datenschrott ergeben, wird spätestens beim Entpacken der Upgradevorgang abgebrochen.) Es wird aber definitiv nicht für andere Versionen klappen, da das Archiv von WPD eine völlig andere Struktur hat.

8. Jott on March 13, 2007 at 11:18 #

   Klappt… Danke!

9. Christoph Voigt on March 13, 2007 at 23:38 #

   Aloah,
   das ganze schaut interessant aus, aber wie schaut es mit einem Backup der alten Dateien aus? Bevor ich rumbastel würde ich gerne wissen ob ein mySQL dump und /wp-admin bzw. /wp-includes vor dem Update gesichert werden.
   Gruß
   Christoph Voigt

10. Alex Günsche on March 13, 2007 at 23:59 #

    Das sollte der verantwortungsbewusste Admin selbst handhaben. Für die Datenbank empfehle ich das Plugin wp-db-backup und dabei gleich die automatischen Backups zu aktivieren. Für das Backup von Dateien gibt es noch kein WP-Plugin; das muss man per FTP selbst machen. (Ich werde evtl. demnächst ein solches Plugin schreiben.)

11. UKStevieB on March 14, 2007 at 00:09 #

    Well that went smoothly, thanks very much for this plugin, it makes upgrading so much easier!

12. Cesar Cardoso on March 14, 2007 at 02:28 #

    Only to say thanks for the plugin! I used it for upgrading to 2.0.7 to 2.1.2 and it went smoothly. Very well done!

13. Frank on March 14, 2007 at 09:31 #

    Für das Backup der Dateien gibt es ein Plugin von Sören Weber, frag mal nach. Ich durfte es testen und es leif super. http://bluesome.net

14. Alex Günsche on March 14, 2007 at 10:36 #

    UKStevieB, Cesar,

    glad you like it. Thanks for the feedback.

    Frank,

    jau, danke für den Tipp. Mal schauen, ich habe noch von WP-Manage noch ein Modul für das Dateien-Backup, was relativ einfach in eine Plugin umgewandelt werden kann und das ich evtl. mit wp-db-backup verschmelzen möchte.

15. Tom Shakely on March 14, 2007 at 13:27 #

    So fantastic! You are a God-send! I’ve been waiting for something like this forever.

16. Fred on March 14, 2007 at 20:05 #

    Wow, you are my hero! I can’t believe how easy it was to upgrade - thank you!

17. Klaus on March 14, 2007 at 20:13 #

    Hallo Alex,

    super Arbeit ! Kompliment ! Läuft wie am Schnürchen ! So etwas kann ‘Otto Normalverbraucher’ wie ich es bin gut gebrauchen.

    Kann es sein, das böse Zungen behaupten, Du würdest Dich bereits auf dem besten Weg befinden Matt den Rang abzulaufen ? ( ok, kleiner Scherz am Rande ).

    Gruesse

    Klaus

    P.S. Problem mit advanced search und seach lite gelöst: Habe die ‘deutsche Sprach version’ aus Deinem plug-in gelöscht, so dass die deutsche und portugiesische Seite auch die englische Sprachversion hat. Die französische Version existiert ja als Uebersetzung und wird auch korrekt angezeigt.

18. Ozh on March 14, 2007 at 21:49 #

    Nice plugin and nicely wrote. I wrote a similar plugin myself, but it’s more a simple wrapper of a bash script that does the “wget” and “tar zxf” dirty work. Your plugin is much prettier.

19. Freesitebuilder on March 14, 2007 at 22:07 #

    This looks very useful. What happens if you are upgrading and want to “skip” a version - for example upgrade from WordPress 2.1 to 2.1.2 (missing out version 2.1.1)?

20. Alex Günsche on March 14, 2007 at 22:27 #

    Freesitebuilder: Usually it’s not a problem to skip a couple of versions when upgrading WordPress (as long as you’re not upgrading from 1.2 to 2.1.2) — independent from the upgrading method you choose.

21. Gene Steinberg on March 15, 2007 at 02:31 #

    I just wanted to say that I tried this plug-in and it works beautifully. The speed was incredible. It seemed to take no more than a minute to download the update and have it fully installed and ready to roll. I’m sold. That is, so long as future updates don’t flummox your plug-in.

    Peace,
    Gene

22. Alex Günsche on March 15, 2007 at 10:05 #

    That is, so long as future updates don’t flummox your plug-in.

    Good point. But I think the basic structure of WordPress will remain the same for at least some more years. Besides, the official upgrade advisories recommend exactly the steps which my plugin performs. Also, I regularily check out the SVN, so I’ve quite a good idea of what to expect from future releases.

23. http://blog.datenschmutz.net/ on March 15, 2007 at 15:11 #

    WordPress Plugin: Instant Upgrading…

    Webapps upzudaten kann manchmal eine nervenaufreibende Tätigkeit sein - will man diesen komplexen Vorgang an Software auslagern? Ja, sagen die Autoren des Instant Upgrade Plugin.
    Das WordPress-Plugin gibt’s in der recht wenig Vertrauen erw…

24. bhlogiston on March 15, 2007 at 15:41 #

    Leider funktioniert das Teil nicht bei mir. Nachdem ich die Installationsanweisung brav befolgt hatte, und nach dem Installieren alle diese files auf 777 gesetzt hatte - beschwert sich beim Klick auf das schöne einfache Udate-Link in der Beschreibung für das Plugin: … writeable by others - und nix ist mit updates. ;(

    ps. Ich kann es nicht glauben. nachdem ich alle monierten files auf nicht zugänglich gesetzt habe - kam der entscheidende dialog - und schwupps. da ist die neueste version. Unfassbar. )

25. Alex Günsche on March 15, 2007 at 15:58 #

    Ich verstehe nicht ganz, was Du da zu beschreiben versuchst. Wenn Du meinst, dass es ein Problem mit dem Plugin gibt, müsstest Du schon etwas genauer ausführen, was Du gemacht hast und was passiert ist.

    Man kann Kommentare auf diese Seite übrigens nachbearbeiten.

26. bhlogiston on March 15, 2007 at 16:40 #

    Ho - nachdem ich jetzt mein geringes Wissen über die Innereien meiner Blogsoftware abgefragt habe - bleibt mir nur, hier nochmal um hilfe anzufragen. Das was vormals die Links waren - ist jetzt eine Blogroll. Und die ist anscheinend beim Update auf der Strecke geblieben. Stattdessen gibt es die Fehlermeldung:

    WordPress Datenbank-Fehler: [Unknown column ‘cat_order’ in ‘order clause’]
    SELECT * FROM wp_categories WHERE cat_ID > 0 AND link_count > 0 ORDER BY cat_order=name ASC

    Wie kann man denn diese Blogroll wieder sichtbar machen - schön nach den alten Rubriken unterteilt? - Ich wäre natürlich sehr froh, gäbe es wieder Links auf meiner Seite.

27. Alex Günsche on March 15, 2007 at 16:43 #

    Du hast einen Blog von 2.0.x auf 2.1.x aktualisiert, nicht wahr?

    Wirf mal bitte einen Blick ins WPD-Forum, das Thema “Probleme beim Upgrade von 2.0.x auf 2.1.x”, insbesondere “meine Blogroll ist weg” bzw. “SQL-Fehler in der Seitenleiste” ist dort schon einige Male behandelt worden. Auch Google kennt das Problem. Kleiner Tipp: Einige Template Tags gibt es nicht mehr, bzw. sie produzieren Fehler.

28. Michael Holdcroft on March 16, 2007 at 09:30 #

    Mein Pronlem ist folgender: Ich habe ein WP version 1.5.2 mit InstantUpgrade installiert. Ich habe ebenfalls alles auf 777 gesetzt und beim klicken auf (Go to Manage » Instant Upgrade) komme ich auf die Manage-Seite, aber es passiert nichts und Instant Upgrade steht nicht im Navigationsleiste. Die Setie ist sonst leer.

29. Alex Günsche on March 16, 2007 at 10:13 #

    Michael: Anscheinend funktioniert das Plugin nicht mit WordPress 1.5.x — es ist offenbar so, dass die Methode zum Einfügen einer Admin-Seite in den älteren Versionen nicht funktionert. Du bist allerdings der erste, von dem ich das höre, daher muss ich darauf wohl in Zukunft hinweisen. Tut mir leid… ich befürchte, Du musst von 1.5.2 auf eine 2er Version von Hand aktualisieren.

30. barney on March 16, 2007 at 10:48 #

    Ok, I give up. What have I missed? I keep getting an error message to the effect of “Access denied. Invalid user name or password.”

    But I haven’t seen any mention of such a requirement anywhere.

    Is a puzzlement.

31. Alex Günsche on March 16, 2007 at 10:50 #

    barney, could you please describe a bit more detailed what seems to be the problem? What exactly did you do, and what happened?

32. Chris on March 16, 2007 at 18:20 #

    I too give up - or maybe hiope for some help by posting here

    Tried downloading the zip fiel but I am constantly told its corrupt (winzip and 7zip). Tried the gz file but WinRar tells me its also corrupt. I can see inside the compressed file that another file eixsits - instantupgrade-0.1.tar[1]

    This is approx 60kb but still its appears corrupt.

    Any ideas or other links to download this from?

33. Alex Günsche on March 16, 2007 at 18:37 #

    Hm, no idea. Have you tried the latest versions of your packaging apps?

34. Chris on March 16, 2007 at 21:12 #

    Yeah upgraded them all. Also tried from 2 different machines using different ISPs so theres nothing common

    Any chance you can email a copy to me and I will host a copy on my server incase others have a similar problem?

35. barney on March 17, 2007 at 03:13 #

    Alex,
    Using Firefox 2.0.0.2 with FlashGot and Free Download Manager (FDM) v 2.0 build 423 - log review produces
    ~~~~~ log start ~~~~~
    20:51:52 2007-03-16 Starting download…
    20:52:04 2007-03-16 GET /download/instantupgrade-0.1.zip HTTP/1.1
    Referer: http://www.zirona.com/download/
    Host: www.zirona.com
    20:52:05 2007-03-16 HTTP/1.1 403 Forbidden
    Date: Sat, 17 Mar 2007 01:53:20 GMT
    Server: Apache
    Content-Length: 416
    Keep-Alive: timeout=15, max=100
    Connection: Keep-Alive
    Content-Type: text/html; charset=iso-8859-1

    20:52:05 2007-03-16 Access denied. Invalid user name or password
    20:52:05 2007-03-16 Stopped
    ~~~~~ end log ~~~~

    If I try the download w/o FDM, nothing happens.

    Using IE 6.0.2900.2180.xpsp.050928-1517 and FDM, same result. Using IE w/o FDM, I get a 72K file, but when I try WinZip, 7Zip, WinRAR, & a couple of others (and different versions for some), a corrupt file is reported.

    Same results for the tar.gz file.

    I find the 403 Forbidden entry in the log interesting, but don’t have any way to overcome that. Best guess is that either the user agent or the server/IP being blocked for some reason. However, considering that there’s at least one other report of difficulty, that would be quite a stretch.

    (Oh, yeah … I also tried supplying an anonymous FTP account with FDM.)

36. Alex Günsche on March 17, 2007 at 12:28 #

    I see. You’re right, I actually do have a list of blocked clients, as I encountered massive sucking from such clients in the past. (Of course, blocking a client by browser string is not a secure solution, but for me, it works so far.)

    Now the 72k file sounds good, but some of you (like Chris, too) appear to have difficulties with unpacking. I don’t quite understand this, but I’ll think of a solution.

37. Charles Stricklin on March 17, 2007 at 19:32 #

    You should probably first backup the database. There are plug-ins that do that already, but if you’re looking to automate this as much as possible, you should consider incorporating that into this plug-in.

    You should also disable all the plug-ins, do your update, then re-enable the plug-ins.

    Finally, a nice feature might be to schedule the update for a time when the load is low. I know I wouldn’t update anything unattended, but maybe someone else might.

38. Alex Günsche on March 17, 2007 at 23:59 #

    Hello Charles,

    You should probably first backup the database. There are plug-ins that do that already, but if you’re looking to automate this as much as possible, you should consider incorporating that into this plug-in.

    I actually had a solution which was designed as “all in one”, called WP-Manage. I decided to drop this in favour of a “do one thing, and do it well” philosophy. I think doing backup should be handled by a single tool, and the admin should set the schedule itself.

    Would I integrate the backup process with the upgrade, there would be two ways for that: First make the backup part of the upgrade, or plug into an existing solution. For the first, this would mean I’d have to build and maintain a backup tool, while there are much better tools available already, and which also constantly improve. Plugging into an already installed solution would mean that I have to decide for one or two implementations, and somehow hack a routine to automatically trigger them. None of both sound like satisfactory solutions to me.

    I think the administrator himself should be able to choose his tools, and set them up appropriately. For example, the wp-db-backup plugin offers the possibility to make automatic backups, and it’s a tested and know-to-work solution.

    I do however recommend a backup as well as the wp-db-backup pluginon the admin page of the plugin.

    You should also disable all the plug-ins, do your update, then re-enable the plug-ins.

    I believe this is an urban legend; I don’t actually see the benefit of this. If you or somebody else can give me reasons for deactivating plugins before an upgrade, please let me know. Of course, plugins may break with an upgrade, but I think it makes no difference whether I deactivate all plugins before, or I remove an offending plugin afterwards. Besides, the upgrading instructions in the readme.html shipped with WordPress also don’t say anything about deactivating plugins.

    Finally, a nice feature might be to schedule the update for a time when the load is low. I know I wouldn’t update anything unattended, but maybe someone else might.

    I also don’t know if it’s a good idea to automatize Upgrades. I think a failing auto-upgrade would be much worse than having a running software with a security hole for some days. I am so convinced that an auto-upgrade is absolutely suicidal that I wouldn’t even implement it as an option — for not tempting the weak, if you know what I mean.

    Now please don’t get me wrong; I’m always open to new ideas. But your suggestions — although each of them definitely worth a thought — are things I already considered, and I think there are some good reasons for my decisions. However, I’m waiting to be proven wrong. If there are more arguments in favour of a certain feature, or if there’s a large request for it, I’ll be willing to reconsider my decisions.

39. barney on March 18, 2007 at 03:41 #

    I agree with Alex on the backup/disabling issues, although from a different viewpoint, perhaps.
    Backup is the operator’s responsibility. It should be a part of normal periodic maintenance, and should precede any sort of installation or update. Adding backup capability to InstantUpgrade would unnecessarily complicate the plugin and diffuse the focus of the product. As mentioned, there are a number of backup solutions available to the blog operator. That operator should use them, rather than ask for added complexity in this product.
    An additional issue with automating backup before upgrade has to do with possible failure(s). If the backup fails, should the product cease operation? In that case, who knows where the backup is in order to make restoration? If the product is sufficiently intelligent to recognize such a failure on a second attempt, should it continue or not? Should it restore the backup and exit? Should it restore the backup and continue? What if the failure point was in the backup?
    Backup is an operator functionality that should not be delegated. Use existing methods and backup prior to running the upgrade.

    Plugin problems are, as they should be, WordPress problems, not InstantUpdate problems. Disabling them, then re-enabling them after an upgrade again adds unnecessary complexity to the product. It also makes any problems more obscure to the operator, since that operator will not know if the problem is attributable to the product or to incompatibilities with the new version of WordPress. If this is a matter of concern, the operator should disable/enable them directly. Don’t try to make the product responsible for actions that should be in the operator’s purview.

    The same arguments apply to _remote_ or _automated_ upgrades. The operator needs to take responsibility for actions in these areas, and to supervise them, not sluff the job off on the product. The less complex the functionality of the product, the less liable it is to fail, and the more likely it is to provide a robust solution.

    Alex, I look forward to a solution of the download problem. I’d be willing to say it’s a problem with my system if it weren’t for the alternatives I’ve tried and the fact that there’s at least one other with a similar problem, although he quoted a 60K file rather than the 72K I see. One other problem I can see is that perhaps my system is trying to transfer the file as ASCII/ANSI rather than binary, but that would have to be a communication issue between the server and the user agent/browser, I’d think. We usually tend to take such for granted. But, then, it’d have to be miscommunication with two different browsers, so that’s another long stretch .

40. joshuayip on March 18, 2007 at 15:55 #

    Yo, thanks a million for this! It will really solve many days of work !

41. Pat on March 20, 2007 at 05:14 #

    After the upgrade, the folders I made readable were all still 777. Should the upgrade program or Wordpress change them back to their original recursive properties or did I miss a step in the instructions?

42. Alex Günsche on March 20, 2007 at 10:09 #

    To be precise, it deletes the old ones, and it creates the new ones with default permissions (cf. umask). Maybe your haven’t reloaded the view in your FTP client. Or your server’s default umask is set to a strange value.

    Anyway, if you want, you can tell me a bit about your server, maybe I can find out something.

43. luca on March 20, 2007 at 10:58 #

    thanks for the plug in. do i need to return all the chmod settings back to what they were, once i have run the plugin?

44. luca on March 20, 2007 at 11:10 #

    i get this message when i try to run the plugin. i have changed all my chmod settings to 777 as recommended

    Fatal error: Call to undefined function current_user_can() in /wp-content/plugins/instantupgrade/admin.php on line 17

    any tips?

45. Alex Günsche on March 20, 2007 at 12:43 #

    Which version of WordPress do you use?

46. Liz on March 22, 2007 at 17:36 #

    Oh… my… goodness…. thank you so, so, so much for this plugin.

    You just made my… well 6 months at least.

    Liz

47. Alex on March 24, 2007 at 06:51 #

    WOW .. but i have not CHOMD all files .. and has worked fine .. only folders and subfolders .. what was under subfolders i did not chomd them to 777 .. was so easy .. wow .. again many thanks .. !!!

48. Alex on March 24, 2007 at 06:54 #

    43. luca - no man .. check .. it’s chomd back to the original

    Everything went smooth. Have fun with your new WordPress version!

    was amazing ..

49. Michael on March 24, 2007 at 08:52 #

    Amazing. Many thanks.

50. http://www.fob-marketing.de/ on March 25, 2007 at 12:14 #

    WordPress automatisch aktualisieren lassen…

    Ich persönlich bin zwar kein Freund von automatisierten Updates, für den einen oder anderen könnte es aber durchaus interessant sein, seinen WordPress-Blog künftig (voll)automatisch auf den neuesten Stand bringen zu lassen.
    Die WordPress-Software w…

51. Oceanwatcher on March 26, 2007 at 01:23 #

    This could be a good start. I will not try it yet, because I have no idea what it does about the fact that the Wordpress .zip files have a folder inside. I still do not understand (and nobody has explained to me) why the developers are forcing Wordpress to be installed into a subfolder?

    Getting rid of that first folder inside the zip file makes a lot of sense. You can then place it and unpack it in any folder of choice.

    And upgrading should be as easy as this:

    1. Check the version running on the server
    2. Check the latest version
    3. Download the upgrade from one to the other (only diff files) as a zip
    4. Unzip with overwrite the zip file in the root of the WP installation.
    5. Done

    This is the way Joomla updates work today and it is really working well. If it works for Joomla, I can not see why it should not work for WP….

52. http://bloganbieter.de/ on March 27, 2007 at 09:58 #

    Wordpress Plugin: InstantUpgrade…

    Endlich kann man das Wordpress Upgrade automatisieren oder zumindest per 1-Click durchführen. Aber wie funktioniert dies? Relativ einfach. Das Plugin lädt die jeweils neuste Version von Wordpress herunter und ersetzt die Dateien auf dem Webserver.
    Th…

53. Joe on April 1, 2007 at 17:57 #

    There is a BASH version and it does the same thing but quick. i built a web version and it even creates a DB backup.

54. Alex Günsche on April 1, 2007 at 18:22 #

    There is a BASH version and it does the same thing but quick.

    1. There are tons of Bash solutions, and as a matter of fact, I also wrote one. But Bash is not an option for most WP users. And a PHP wrapper for a Bash script is just ugly.
    2. On my server, the upgrade with Instant Upgrade takes less than 5 seconds, maybe a bit more on other hosts. Even if the bash solution is faster, who cares about a few seconds? By the way, what preparations does your Bash script perform? Can you show us the source code?

    i built a web version and it even creates a DB backup.

    I also had an all-in-one solution called WP-Manage. And it didn’t only do a DB backup, but it also backed up the files. But I dropped this in favour of a standalone solution for upgrading.

55. Simon on April 3, 2007 at 15:22 #

    hi

    i’ve just run it and it works like a dream - thanks!

    one thing i’ve noticed is that the root directory with my blog in it stays at 0777 and the owner doesn’t change to apache (unlike all the sub-directories) - is this still safe?

56. Alex Günsche on April 3, 2007 at 16:11 #

    Simon, you might want to read a post I wrote recently regarding this and other issues.

57. Evan on April 3, 2007 at 19:44 #

    Excellent plugin!

    Thank you!!!!

58. Libretto on April 3, 2007 at 22:19 #

    Je viens de faire une traduction de cette page en frrançais.
    Thanks for this great plugin !

59. Joe on April 3, 2007 at 22:20 #

    Yeah, it does the backups too. The web wrapper looks nice. Its simple, it allows users to configure and then run the script. But I do have to agree with you that most users will just do the plugin since its right there. But I like the bash script because I can upgrade all my wp sites at once. its all done - backups of both the directorys and the db for every site gziped. Then upgraded in under two minutes.

60. Ryan on April 4, 2007 at 05:19 #

    I tried to download this plugin, and it seems the zip file is corrupted. For me, at least.

61. Alex Günsche on April 4, 2007 at 09:33 #

    Libretto, c’est une très bonne idée, ça. Merci beaucoup pour la traduction! Je vais includer un lien vers ta traduction dans le tuto la-haut.

    Ryan, have you tried with the latest version of 7zip?

62. sepa on April 4, 2007 at 13:26 #

    Hi Alex,

    I tried to use your plugin to update my 2.0.7 version. During download of the latest version I got an error 110. So I downloaded the file manually. I placed it twice in the work directory, first as ‘latest.zip’ and after that as ‘wordpress-2.1.3.zip’. In both cases the script continues after the 110 error and says that it loaded the local file. After that the script canceled, saying that there was an error downloading the file. The update wasn’t performed.
    All permissions were correct (777) as well as the zip files. Using them for a manual upgrade went well.

63. Alex Günsche on April 4, 2007 at 13:36 #

    sepa, did you make the new WordPress package writable, too? It is correct that the plugin tries to download the package from wordpress.org (again), before checking for a local copy. But afterwards it should find the local copy, and it will first check if that file is writable. Was there possibly an error message of that kind? If not, could you possibly upload a screenshot of when using the local file failed?

64. Patrick on April 5, 2007 at 17:38 #

    Works fine, thanks
    Just a problem, I don´t have anymore autorization on my files !!!

65. Alex Günsche on April 5, 2007 at 21:29 #

    Patrick, if you had read the instructions, you would have known that before. However, you can regain control over your files by reading and following the instructions in the lower part of the plugin’s management page (in your admin panel: Manage » InstantUgrade).

66. andy on April 5, 2007 at 23:26 #

    After dealing with problem how to apply chmod 777 to all my subfolders i could do it with SmartFTP . It worked flawlessly afterwards.

67. Gene Steinberg on April 6, 2007 at 15:40 #

    I installed the update from version 0.1 per your instructions, but the version number displayed in my plug-ins panel is the same. Did you miss something? Did I miss something?

    Peace,
    Gene

68. Alex Günsche on April 6, 2007 at 18:02 #

    Gene, thanks for the hint, I forgot to increment the version number.
    Did that now and re-uploaded.

69. Holly on April 7, 2007 at 08:45 #

    Well, it worked fine.
    Then when I was unable to change the CMOD back (permission denied) I tried to go to the admin page to change the settings there.
    No go, I am completely locked out. Can not log in through Admin, can not even see what is in the folders (SmartFTP)
    Short of deleting the whole site and reinstalling - do you have any suggestions???

    -Holly

70. Alex Günsche on April 7, 2007 at 11:06 #

    Yes, there is a fallback solution since v0.2. Take the file chmod.php and place it in your WP base folder. Then open the file in a text editor and follow the instructions there.

71. Holly on April 7, 2007 at 14:51 #

    I had to reload everything. the access denied included my WP base folder. I just established a new folder in my root and reloaded everything from my computer (renaming a few locations)
    Backup is really important.
    Don’t know if it was peculiar to this particular Apache server version, but the hijack was not fun.
    Now that I have how to restore it down, I might even be willing to try it again at the next update.
    -Holly

72. Alex Günsche on April 7, 2007 at 14:55 #

    Hm, is it possible that you set the folders’ permissions to 0666 instead of 0777? This would explain it, especially the issue with the base folder.

73. http://polskiblogger.pl/ on April 7, 2007 at 15:15 #

    Automatyczna aktualizacja WordPressa…

    Koszmar. Tak, krótko i zwiÄ�źle można określiÄ� dośÄ� czÄ�ste aktualizacje WordPressa. Mimo iż nie sÄ� one wyjÄ�tkowo skomplikowane to i tak fajniej by było gdyby można było to zautomatyzowaÄ�. Otóż można!

    The InstantUpgrade plugin
    The Ins…

74. Holly on April 7, 2007 at 20:29 #

    no, there is no possibility of a leading zero in the CMOD settings. The selectio is done by checking boxes.
    But since WordPress was not in the root directory, but in its own folder, the rest of my sites were not affected.
    And it was a good learning experience to do a complete recovery. I had gotten a bit sloppy about backups.

75. Per Ejeklint on April 8, 2007 at 11:39 #

    Thank you for this lovely plugin! WP upgrading just became pleasant. Excellent work!

76. Edwin on April 8, 2007 at 22:17 #

    Unfortunatly this is not going to work on my host. They have a thing called phpsuexec installed, and the server doesn’t allow 0777 files.

77. Robert Richard on April 9, 2007 at 00:31 #

    Hello,

    Attempted my first Instant upgrade tonight. Will I have to chmod folders and files to 777 every time I need to upgrade WP. If yes, might as well use my old method, doing it manually. What do you think? It seems be working well up to now.

    Marvelous!

78. Alex Günsche on April 9, 2007 at 18:15 #

    Edwin, if you have phpsuexec, you probably don’t need to chmod your files. This is also mentioned in the tutorial.

    Robert, no, permissions will only have to be changed once.

79. ovizii on April 10, 2007 at 09:17 #

    regarding the rights of files and folders:

    generally 0777 is way too much, i.e. on my Debian box I set the group of the web/ or htdocs/ or public/ folder (whatever it is called on your system) to www-data which is the user apache2 runs as (this might differ with your os) and the user to the user that owns that vhost, aka chown -R web1_admin:www-data web/ and then give full rights to owner and group with chmod -R 775 web/

    so others only have “5″ as right

80. mic on April 10, 2007 at 11:43 #

    hi alex! nach einem solchen plugin hab ich bereits die ganze zeit gesucht …vielen dank dafür. cheers, mic

    update: es hat bei mir übrigens auch ohne (!) die dementsprechende rechtevergabe funktioniert! wenn ich “wp-admin” auf 777 setzen wollte, bekam ich vom server eine fehlermeldung retour.

81. Martin Schindelholz on April 10, 2007 at 15:34 #

    Hallo Alex

    Gibt es eine Möglichkeit InstantUpgrade zu benützen auch wenn safe_mode=on ist?

    Gruss
    Martin

82. Alex Günsche on April 10, 2007 at 15:37 #

    Martin, diese Möglichkeit wurde mit 0.2 deaktiviert, da es mit safe mode unberechenbare Fehler gab.

83. Martin Schindelholz on April 10, 2007 at 15:59 #

    Hallo Alex

    Schade!
    Gibt es Grund zur Hoffnung auf die Version 0.3?
    Oder gibts einen work-around?
    Ich hab das Plugin bei einigen Kunden einsetzen können und möchte es nun bei den anderen Providern auch einsetzen.

    Gruss
    Martin

84. Alex Günsche on April 10, 2007 at 16:15 #

    Schau mal in die admin.php, dort musst Du die entsprechende Passage rausnehmen. Ohne Gewähr und ohne weiteren Support.

85. Robert Richard on April 11, 2007 at 13:50 #

    Hello,

    Is WordPress plugins deactivation needed when updating WordPress via Instant Upgrade? The Instant Upgrade plugin is a savior for me as I maintain 4 WordPress sites.

    Thanks for your reply.

86. Claude Gelinas on April 11, 2007 at 16:43 #

    No plugin deactivation was needed here.

    This install worked fine on both my English and French WordPress installs so I can confirm the process is lightning fast and amazingly painless. In this particular case, I used “InstantUpgrade” when going from WP 2.1.2 to 2.1.3 and it went perfectly.

    Thank you -very much- for this indispensable plugin ; )

87. Kaonashi on April 11, 2007 at 21:06 #

    Wow! This totally rocks! I used to spent not a lot but still some time on first upgrading my local WordPress-installation (my testing environment), carefully deleting and copying the right files, and then repeating the same process online. Now it’s just a single click in both environments and without any further effort the update’s being done. Thanks a lot!

    BTW: My online installation runs on simple GoDaddy-hosting account. Your plugin worked like a charm without me modifying any file permissions.

88. Arby on April 11, 2007 at 23:05 #

    Hi Alex,
    das Plugin ist genial! Danke dafür, damit hast du mir eine Menge Kopfschmerzen erspart.
    Ich hab mich ja darauf eingerichtet, dass es nicht klappen würde, denn mein Wordpress läuft nicht unter Linux, sondern unter Windows Server. Damit bin ich wohl ein Exot. Aber mein Upgrade von 2.1.2 auf 2.1.3 hat tatsächlich geklappt.
    Noch ist mein Wordpress-Blog nicht aktiv (derzeit blogge ich noch auf Blogspot), aber es gibt schon Test-Inhalte, so dass ich das Upgrade live ausprobieren konnte.

89. Ed on April 12, 2007 at 00:20 #

    Hi. I have had a big problem with your plugin. I did everything you said word for word. It didn’t seem to download anything at all. And now I have no admin screen. When I log in to wp-admin I get taken to a blank page (I see the theme but no content) and the address bar stays as www.born-of-frustration.com/wp-admin.

    What have I done and please, please, how do I fix it?

90. Alex Günsche on April 12, 2007 at 08:44 #

    Arby, gut zu wissen, danke! Bin zwar selbst kein Windows-Freund und würde es nicht mal mit der Kneifzange anfassen, aber es freut mich natürlich, dass das Plugin auch auf dieser Plattform funktioniert.

    Ed, if it wouldn’t have downloaded anything, it wouldn’t have deleted your files. Did you get a results screen? If so, what did it say? Could you please describe more specifically what has happened? In the meantime, I suggest you download all WordPress files (wp-admin, wp-includes, files in base folder) and upload them again. If this is not possible because of permissions, copy the file chmod.php into your WP base folder and read the instructions at the beginning of that file. Hope this helps.

91. Jerry on April 12, 2007 at 09:15 #

    Hi, it worked like a charm! I had originally done an upgrade from 2.1.2 to 2.1.3 manually and messed up something (a few things stopped working properly), but then I let your plugin do the same upgrade again (this time 2.1.3 -> 2.1.3) and now everything works perfectly. Excellent plugin, and so fast! Thanks!

92. MAWSpitau on April 12, 2007 at 10:29 #

    Hallo,

    ich würde das plugin gerne testen, aber leider erhalte ich vom plugin die Nachricht, ich möchte doch bitte den safe_mode ausstellen. Das Problem an der Sache ist aber, dass dieser laut phpinfo() auf off steht… Kann mir da einer einen Tipp geben?!

    Vielen Dank und bis dann
    MAW

93. Alex Günsche on April 12, 2007 at 11:05 #

    MAWSpitau, wenn Du magst, kannst Du — auf eigene Gefahr — in der admin.php den Teil mit der safe-mode-Abfrage entfernen.

94. MAWSpitau on April 12, 2007 at 11:59 #

    Moinsen.

    Ich mag den Zusatz — auf eigene Gefahr — nicht

    Jo, kann ich machen und werde ich auch mal versuchen, aber was kann denn da los sein? Wieso zeigt der an safe_mode wäre an… schon komisch, oder?

    MAW

95. Alex Günsche on April 12, 2007 at 12:05 #

    Hm, vielleicht werden auf Deinem Server die ini-Werte falsch ausgegeben. Oder es ist so, dass der globale Wert deaktiviert und der lokale aktiviert ist.

    Was gibt denn Dein PHP bei var_dump(ini_get('safe_mode')) aus?

96. MAWSpitau on April 12, 2007 at 12:17 #

    string(3) “Off”

    Das wirklich kuriose ist, wenn ich den Teil auskommentiere:

    if ( ini_get('safe_mode') ) {
$this->log_messages[] = sprintf( __('Error: The PHP Safe Mode is active on your host. Performing file operations while safe mode is enabled ca n lead to unexpected results. Therefore, this plugin will refuse to work when safe mode is enabled. If you want to use t his plugin, please tell your hoster to deactivate safe mode.’, ‘iu’), ABSPATH );
$this->log_messages[] = __(’The upgrade process has been aborted, no modifications to your files or datab ases were applied.’, ‘iu’);
$this->errors = true;
return false;
}

    kommt dennoch die Meldung…

    Safe Mode active

    The PHP Safe Mode is active on your host. Performing file operations while safe mode is enabled can lead to unexpected results. Therefore, this plugin will refuse to work when safe mode is enabled. If you want to use this plugin, please tell your hoster to deactivate safe mode.

    Es scheint, als wäre irgendwo ein dicker WURM drin.

    MAW

97. MAWSpitau on April 12, 2007 at 12:41 #

    Jetzt habe ich den Kram auch in der admin.php deaktiviert und nun scheint es zu gehen…
    WP 2.1.3 installiert. Thumbs up!

98. Alex Günsche on April 12, 2007 at 12:43 #

    Es ist wohl tatsächlich so, dass Dein Server einen ungewöhnlichen Wert zurückgibt. Statt eines Strings sollte es eigentlich der Integer-Wert 0 oder der Boolsche Wert false sein. Kannst Du mir mehr über Deinen Server erzählen?

    Habe übrigens vergessen zu sagen, dass Du auch in der upgrade.php Zeile 181ff. (in v0.2) enfernen musst.

99. Oscar on April 12, 2007 at 15:45 #

    Wow! This is awesome. Thanks so much for doing this. I greatly appreciate it. It works flawlessly. Awesome job!

100. Ed on April 12, 2007 at 17:42 #

     Hi again. Basically my blog was working fine. I installed your plugin, activated it and started it up. The screen went blank for a second and my wordpress dashboard disappeard. So I don’t have any access to my admin panel.

     Now I can’t log in to my wp dashboard at all. I just get a blank page.

     As for re-installing. I used fantastico to install it so not sure how to do it. And wouldn’t this overwrite all my previous work on my blog?

101. Jan on April 12, 2007 at 19:58 #

     Alex, you are my hero! It didnt work flawlessly for me the first time, but OMG this plugin simply rocks!

     I ran the plugin on a few WP’s of differing versions, here are few issues: (hoster: domainfactory (afaik, a chroot environment), using php4 and safe_mode=off)

     1) insert a check for MySQL version:
     I upgraded a WP from 2.0.2 to 2.1.1 and it said 2.1 needs MySQL 4 (I was running 3.x for this domain). Copying/using/implementing wp_check_mysql_version() from wp-admin/upgrade-functions.php might just do the trick. Might be helpful to some if warned about this before attempting upgrade.
     2) get_bloginfo(’url’) not working:
     I keep WP usually at domain.com/wp/ and blog under domain.com/ and for some reason ABSPATH gets it; get_bloginfo(’url’) is the culprit. Had this problem with a few other plugins as well and usually I manually change the path. This is sofar a problem for me because the plugin couldnt find /wp-admin/upgrade.php (which I ran manually, so not that a big problem).
     Fix suggestion: in upgrade.php, lines 326-328 replace “get_bloginfo(’url’)” with “get_bloginfo(’wpurl’)”. It works perfectly for me. This should take care of “- support different ‘home’ and ’siteurl’” in TODO as well. (I keep my fingers crossed)
     3) feedback to user
     wp-db-backup has this neat little progress-meter when backing up, this would be an insanely cool feature for your plugin. Also, IU says “Checking if …” but not (for all items) if it was successful or not, a “Yes!” or “No ” would totally suffice to inform people better what went wrong.
     4) simply exectute ?
     typo in upgrade.php, line 328
     5) the chmod’ing
     Please clear up what exactly to chmod (more precisely, how deep). I nearly went crazy chmoding all and every subdirectory and file under /wp/ at first (tinymce is a killer), then later realised it wasnt needed when I experimented on some blogs to only chmod the main dir’s. I am not that familiar with chmod, but wouldnt chmod’ing of only the top-dirs be enough?
     6) upgrade.php, line 49: change version to current one.

     Sorry that I am quarrelling about these issues, but at least I hope it is (somewhat) constructive feedback.
     I truly believe that you are making a real change here. This is the (next) killer-feature of WP and I - and everyone else, I hope - just plain loves it! Keep up the good work!

102. Alex Günsche on April 12, 2007 at 21:09 #

     Ed, you must access your website via FTP, then delete the directories wp-admin, wp-includes and the files in the WP base folder (don’t touch wp-content/ and wp-config.php). Then you unzip the new WP version on your local computer and upload all files from there, except wp-content/. Then open http://example.com/wp-admin/upgrade.php in your browser. Your data are not affected as they are stored in the database and will remain intact.

103. Alex Günsche on April 12, 2007 at 21:16 #

     Jan,

     Thank you for your feedback.

     1) insert a check for MySQL version:

     Hm, I don’t know… this is a very specific issue, and it’s the admins duty to check if the new version is compatible with his/her host. It would also have to be done on a manual upgrade. But I definitely should issue a warning to check for compatibility.

     2) get_bloginfo(’url’) not working:

     This is an important issue, supporting installations with different siteurl and home, and it’s on my list. I’ll check your suggestions regarding that.

     3) feedback to user

     Improving the look’n'feel is definitely on my list, too. I know that behaviour of wp-db-backup, I like it, and I could well imagine to implement something like this.

     4) simply exectute ?

     ;)

     5) the chmod’ing

     It is explained in the tutorial. Proper FTP clients should be able to do this recursively, so you would just give the top-level directory.

     6) upgrade.php, line 49: change version to current one.

     Right.

     Sorry that I am quarrelling about these issues, but at least I hope it is (somewhat) constructive feedback.

     Oh, your feedback is very much apprechiated. Thanks again!

104. Sinklar on April 13, 2007 at 21:56 #

     Hi.

     I’ve just installed your plugin. Thank’s for that, but…

     Can you tell me how to manually remove it or undo steps ? Does it write any special .htaccess ?
     Yes, I have a problem : a beautiful “500 Internal Server Error”…

105. Sinklar on April 13, 2007 at 22:17 #

     Ok, I’ve just got it to work.
     Had to delete and replace some files.
     So as usual, chmod is dangerous.

106. Steven on April 14, 2007 at 19:29 #

     I’m confused. Why not use such functions as ftp_connect() or the chmod method if the FTP library is not installed on PHP?

     http://php.net/ftp

107. Alex Günsche on April 14, 2007 at 21:37 #

     Steven, this will be a feature of the next version. However, we will not use ftp_connect(), but raw FTP commands via fsockopen(), as this will support a wider range of servers.

108. http://www.wordpress.gr/ on April 21, 2007 at 15:54 #

     Ευκολότερη διαδικασία αναβάθμισης…

     Φαίνεται πως οι δημιουργοί του WordPress προσπαθούν να κάνουν την διαδικασία αναβάθμισης όσο το πιο δυνατό ανώδυνη μέσα από τις αναμενόμενες …

109. Rod on April 28, 2007 at 14:28 #

     I just installed and used the plugin… everything went well, it was as simple as any other plugin being used. ? though… is it safe to disable the plugin once the upgrade is complete?

     Again, thnk for a well written plugin and installation notes.

110. Michael on April 30, 2007 at 15:32 #

     Hi Alex, ich wollte mich nur kurz für Dein tolles Plugin bedanken, findest Du auf unserer Seite unter den “must have” wordpress plugins

     Sonnige Grüße,
     Michael

111. SEM Mexico on April 30, 2007 at 18:30 #

     Simply Amazing!:)
     One click and you have the latest WordPress Version running smooth.
     Congratulations! you have developed a great plugin.
     I´d like to help spread the word out, i´ll make a post in my Blog and if you Guys want a little help. i could help you to transalte your documentation into spanish.
     Thanks for all your effort!
     Marcelo Waldo.

112. ovizii on May 8, 2007 at 08:34 #

     hi there.
     can you tell me how you check if the folder: wp-content/plugins/instantupgrade/work/ is writeable by the webserver? I get this error:

     Error: The work directory wp-content/plugins/instantupgrade/work/ is not writable by the webserver. This upgrade procedure requires write access to this folder. You should set the file permissions mode to 0777.

     The upgrade process has been aborted, no modifications to your files or databases were applied.

     But the fodler is writeable, it is owned by my user and by the webserver group therefore a chmod 775 is enough. I don’t want to make it writeable by everybody…

     I found the error: the work folder was not automatically created.

     seems to have worked, here is the last problem:

     Running upgrade script of new WordPress version…

     It was not possible to execute the WordPress upgrade script, possibly because remote file access is disabled. This is not tragic, simply exectute the upgrade script manually to finish the upgrade.

     ok, manually triggering the upgrade script worked. one small glitch though: the link to the upgrade script was not right. my installation is like this: mysite.com/wordpress/ but the blog root is inside mysite.com/ the script did not detect this and sent me to mysite.com/wp-admin/upgrade.php but it should be like this: mysite.com/wordpress/wp-admin/upgrade.php

     otherwise great plugin, worked perfetcly.

113. Sergio on May 10, 2007 at 18:46 #

     Hi,

     I just want to know if the plugin deletes *all* files or just the Wordpress files (I haven’t seen nothing specified, sorry).

     Thanks a lot for this great plugin.

114. nepf on May 15, 2007 at 11:56 #

     Hallo Alex,
     danke für das geniale plugin. Das könnte ich für meine diversen WPs gut gebrauchen.
     Allerdings ist es so, dass ich immer ein ganz paar Änderungen habe (z.B. am TinyMCE) - das ist dann doch mühsam umzusetzen wegen der Besitzerrechte …

     Frage:
     Kann ich vor dem upgraden mir meine geänderte WP_Version auf meinen server packen und das plugin anweisen, das zip von da und nicht von wordpress.org zu saugen?

     Wo muss ich ggf. den Pfad anpassen?

115. Alex Günsche on May 15, 2007 at 22:01 #

     Ja, in der Datei upgrade.php, Zeile 339 bzw. 340 kann man einen anderen Server bzw. ein anderes Paket definieren.

116. Twolane on May 16, 2007 at 02:15 #

     I just this minute used your InstantUpgrade0.2 plugin to update to 2.2 from 2.1.3. The upgrade went flawlessly. I use lunarpages.com as my blog location, and I had absolutely no changes or modifications to make to the installation to get your plugin to work.

     Thank you so much for making this software available and for making WordPress upgrades simple and effective.

117. liciece on May 16, 2007 at 10:15 #

     i used it for a long time…i believe that it is a quite useful tool for upgrading wordpress…

118. BobWms on May 16, 2007 at 14:58 #

     Thank You!!

     Just used your plugin to upgrade from 2.1.3 to 2.2. Followed directions and it worked absolutely flawlessly in a shared linux hosting environment.

     I am very grateful.

     Thanks Again!!

119. Peaceful on May 16, 2007 at 18:28 #

     Once again. A perfect one-click-upgrade thanks to your plugin.

120. eduo on May 16, 2007 at 20:14 #

     Ok. Your plugin is scary. I actually thought it had failed. The whole download and upgrade process took 9 measly minutes.

     Note: Some hosting places have some really strange permissions for compressed files (lsz), these can make the upgrade fail. The files can’t be deleted in my situation so I moved it and ran the update immediately (they will be generated almost instantaneously).

121. Nebur on May 16, 2007 at 23:52 #

     I can’t upgrade. I upgraded using this plugin to 2.1.3 version, but now that the 2.2 is out, i wan’t to upgrade and i can’t. I go to Manage-InstantUpgrade and then i click in The latest and greatest WordPress ever, please. and then click in Upgrade my Wordpress and it just stays in a page with

     Instant Upgrade

     With InstantUpgrade, you can upgrade your WordPress installation to the latest or an arbitrary WordPress version with a single click.

     any help? Please :’(

122. Alex Günsche on May 16, 2007 at 23:56 #

     Nebur, which version of InstantUpgrade do you use? Have you modified the file in any way? Have there been changes to your server?

123. Nebur on May 17, 2007 at 00:04 #

     I use v0.2 of InstantUpgrade. And i only modified the sidebar in my theme, that’s it. I tought that maybe where the files permissions, but they are in 777. What can i do? Should i delete the InstantUpgrade plugin and upload it again?

124. Alex Günsche on May 17, 2007 at 00:23 #

     Yes, you might try that. If it doesn’t work, would you give me access to your blog? I could take a look myself. If you want, you can send the details encrypted via my comment form. If you don’t want to, I’ll understand that, but I won’t be able to help you.

125. Nebur on May 17, 2007 at 00:37 #

     Ok, just let me know the data i must send you. Only the wordpress user and password or the FTP user too?

126. HART (1-800-HART) on May 17, 2007 at 06:52 #

     Greetings! I sure would like to test this plugin, but when I download the “.zip” file .. I get an invalid archive? WinZip won’t unzip it. RAR does, but the file inside is not a php file. Can you please advise?

     Thanks in advance.
     \HART

127. Alex Günsche on May 17, 2007 at 10:24 #

     Nebur: The WP login should be sufficient for the beginning.

     Hart: Have you tried 7zip?

128. Nebur on May 17, 2007 at 16:32 #

     I sent you the info in the comment form. Thank you very much for your help

129. Nebur on May 17, 2007 at 17:44 #

     Thank you very much for your help, after i deactivated all the plugins everything went smooth. You’re the man!

     edit by Alex: I suppose this was a memory issue or some hickup on the server. There was no indication of a conflict, and I assume that there were just too many plugins loaded, so the upgrading died when trying to load.

130. HART (1-800-HART) on May 17, 2007 at 18:21 #

     Alex .. I’ve never tried 7zip .. but I just downloaded the .7z archive and my winRAR managed to extract the files. I will be trying to upgrade http://1800hart.com/picks/ today with the plugin, then hopefullythis can help me about 30 other domains! // Thanks for the plugin

131. HART (1-800-HART) on May 17, 2007 at 18:55 #

     Wow.! Success. Although it took me 20 minutes to make all the files writeable with my WS_FTP_LE version … I had to manually chmod the files and subdirectories individually. The upgrade took 20 seconds. I guess I will try with FileZilla or a different FTP program to help me with the slow part.

132. Amine on May 20, 2007 at 19:34 #

     Wonderful!
     it worked perfecly smoothly
     Thanks a lot

133. http://www.filination.com/ on May 21, 2007 at 13:45 #

     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…

134. Florian on May 21, 2007 at 14:09 #

     Hallo!

     Tolles Script, leider werden die Rechte nach dem Update nicht geändert, so bleibt alles CHMOD 777.

     Gibt es dafür eine Lösung, oder wie bekommt man die Rechte wieder richtig gesetzt?

     Gruß!

135. Alex Günsche on May 21, 2007 at 14:40 #

     Florian, normalerweise sollten alle Rechte wieder auf 644 sein, da die Dateien neu angelegt werden. Nur das WP-Wurzelverzeichnis selbst bleibt auf 777. Entweder hat bei Dir der Upgrade-Vorgang nicht funktioniert (dann solltest Du eine Fehlermeldung bekommen haben), oder aber Dein FTP-Client zeigt noch die alten Werte an.

136. Florian on May 21, 2007 at 15:45 #

     Hi Alex,

     das Update hat wunderbar geklappt. Bekam keine Fehlermeldung. Mein FTP-Programm (Filezilla) zeigte mir aber in der Tat noch die alten Werte (CHMOD 777) an.

     Ist also alles glatt gegangen und es ist alles wieder auf 644 und es nur ein Anzeigefehler von Filezilla?

     Tausend Dank im übrigen für dieses Plugin, das beste was mir bisher in die Finger gekommen ist!

     Finde es auch klasse, das du hier ein wenig Support gibst!

     Gruß!

137. hombrelobo on May 21, 2007 at 23:01 #

     Excellent.

     I found an problem, though. My blog is in Spanish, and when I tried to upgrade the language file, since the user now is apache, I do not have access to it.

     I know the workaraound … but sounds too much just to upgrade the language file ……

138. Gelan on May 24, 2007 at 08:09 #

     Thanks for this script! I was STUNNED at how fast it was… It was done in a blink of an eye… You’ve done a fantastic job with this. Much better/easier than my host’s Fantastico deal.

     Thanks again!

139. Ursula Hoffmann on May 24, 2007 at 17:41 #

     Gut gemachtes Plugin, wurde sogar darauf hingewiesen die PHP safe-mode zu deaktivieren, etwas, das ich beim Domain Setup beim V-Server von Strato immer vergesse. Alles lief gut, bis ich meine eigenen wp-admin-css-files wieder per FTP hochladen wollte - kein Zugriff! Auch löschen war nicht möglich.
     Auch das chmod resetting wurde mit error in einer File abgelehnt.

     Momentan rotiert man da etwas. Ein Normaler Boot im Recovery Manager des Servers im Strato Administrationsbereich hat alles wieder in Gang gebracht. Vielleicht sollte man diesen Tipp in die Dokumentation aufnehmen, es erspart das chmod resetting.

     Dokumentation

140. Brian on May 26, 2007 at 20:23 #

     Worked Great! Thanks! This is a real time saver.

141. Véronique on May 31, 2007 at 03:45 #

     HI ! well ! it´s don´t work, I downloaded the zip file, unziped, but it´s only one file about 85 kb without extension, it´s not PHP or something ! and the others compressed files is corrupt !
     ANd when I put this small file in the correct directory in my server, it´s never appears in Wordpress Plugin Setup Page because it´s not a valid file.

     Please help me ! what can I do ? can you send me the good files to my mail ? or tell me where I can download-it.

     Tks, and I’m waiting your help Ok !
     Veronique - From Sao Paulo - BRASIL

142. Chris on June 7, 2007 at 21:11 #

     Danke! Genau das Plugin das ich brauchte!

143. HART (1-800-HART) on June 20, 2007 at 18:34 #

     This plugin really helps me save time upgrading to new versions.

     Although, there is one issue that I hope you consider for future upgrades or releases … it has affected me.

     I use a few other plugins (WP-Print, Iimage Browser) that requires placing files in the WP-ADMIN folder. I wish there was a way to designate certain files as ones that are prevented from being upgraded - maybe it can copy them to your /work folder before deletion of wp-admin and then put it back?

     If there is a way to do that now .. can you please advise?

     Thanks for the plugin!

144. Alex Günsche on June 21, 2007 at 15:59 #

     No, there is no way to do this automatically now, but it is on my agenda for one of the next releases.

145. pross on June 21, 2007 at 21:07 #

     Hi, 1st great plugin!
     I get only one error, the updater leaves wp-admin folder chmodded to 744, which on my webserver is unservable, DIR’s need to be 755…

146. Alex Günsche on June 22, 2007 at 00:26 #

     Oh, that’s not so good… could it be that there is a problem with your umask setting?

     I guess, I could make the InstantUpgrade plugin itself ensure the permissions are set correctly… putting this on the todo list.

147. pross on June 22, 2007 at 13:34 #

     where is this umask setting?

148. hombrelobo on June 22, 2007 at 14:24 #

     Fantastic plugin, really fantastic.

     But as BART says, would be nice to be able to have some files “untouched”.

     For instance, I modify my feed.rss2.php files to include ads in my feeds. And every time I use Instant Upgrade, the modifications disappear. Even worse, since the new owner of the files is apache, I have to manually change the owner (chown) for those files and modify them again.

     In spite of this, I love your plugin so much that it is worth doing it …

     But maybe for next version ……

     Thanks

149. pross on June 22, 2007 at 14:52 #

     Just top add to what i posted earlier, it wasnt just the wp-admin folder that was 744, its all folders under wp-admin and wp-includes!
     I’m sure this didnt happen with 0.1
     My system is a VPS running apache2 suPHP 5.2.3 with suhosin

150. Alex Günsche on June 22, 2007 at 15:57 #

     When did you install Suhoshin? Could you deactivate it and try again? There were definitely no changes between 0.1 and 0.2 that affect chmod and umask. It could be that Suhoshin has automatically set a higher umask, resulting in lower permissions for newly generated files. But 0744 for directories is definitely wrong and unusual.

151. pross on June 22, 2007 at 16:28 #

     suhosin is installed as the hardened patch, going to recompile PHP without it then try the plugin again

152. pross on June 22, 2007 at 16:54 #

     still the same with no suhosin at all, here is a link to my phpinfo

153. pross on June 22, 2007 at 17:12 #

     SUSSED IT!
     You were right about umask in suphp.conf umask was set to 0033 i changed it to 0022 and everything works perfectly! Strange thing is ive never edited suphp.conf ?!?

154. nepf on June 24, 2007 at 19:00 #

     Hi Alex,
     mit Deiner Hilfe (s. 15. Mai) konnte ich es realisieren, dass das Plugin “mein” upgrade-Paket lädt - super Sache!

     Einen Schritt weiter. Das Plugin “verschont” doch das Sprachfile - stimmts? Das würde ich gern umgehen, damit immer “mein” aktuelles Sprachfile aus meinem Paket übernommen wird.
     Was mss ich tun?

155. Jerry on June 25, 2007 at 01:34 #

     How do we know what permissions to set all the files and folders back to after the upgrade? Do you have a table to refer to that shows the default permissions settings for the full Wordpress Installation?

     It seems you are suggesting we leave everything writeable. Does that not pose a security risk?

     OR, does the upgrade script set the permissions back to more secure values? You seem to suggest something to that effect, but I’m not sure … What do you mean by “take control of the files…”?

     As soon as you changed the file permissions, you should run the upgrade routine once (you can choose your current version, if you want). This will make the server take control of the files and protect them against being modified by other users.

156. Alex Günsche on June 25, 2007 at 10:32 #

     nepf, in der Datei iu_class.php gibt es zwei Zeilen, die das machen: eine für das Extrahieren, die andere für das Wiedereinfügen. Die musst Du entfernen bzw. auskommentieren.

     Jerry, there is a recent article which should answer your questions.

157. sascha on June 25, 2007 at 14:30 #

     Frage: Habe das Pugin wie beschrieben als zip. gedownloaded, extrahiert und in das Pluginverzeichnis vom Server (mit SmartFTP) eingefügt. Wie beschrieben, die erforderlichen Dateien beschreibbar gemacht - aber nichts passiert im Endeffekt. Im Admin-Bereich mit F5 alles aktualisiert - aber keine updatemöglichkeit gefunden. Wie kann ich dieses Problem lösen? bin Anfänger…!

     Danke, Sascha.

158. Alex Günsche on June 25, 2007 at 14:38 #

     Hast Du es denn auch aktiviert?

159. sascha on June 25, 2007 at 14:50 #

     in dem admin Bereich in WP unter Plugins? ja!

160. sascha on June 25, 2007 at 14:57 #

     muss noch anmerken, dass ich mir die site habe bauen lassen - könnte es evtl. damit zu tun haben, dass ich möglicher Weise nicht ALLE Rechte habe??? oder ist das davon unabhängig?

     BG, sascha.

161. Alex Günsche on June 25, 2007 at 15:02 #

     Wenn Dir ein Dienstleister das WordPress eingerichtet hat, solltest Du Dich an ihn wenden. Ich kann leider nicht raten, was er an Deiner WP-Installation gemacht hat.

162. sascha on June 25, 2007 at 15:08 #

     habe meines Erachtens erweiterte Zugriffsrechte, dennoch keine Ahnung weshalb das Plugin nicht arbeitet. nur um nochmal sicher zu gehen:

     zip. downloaden
     extrahieren->mit FTP-Programm ins Pugin-Verzeichnis kopieren
     sämtliche Ordereigenschaften (außer wp-congig.php) beschreibbar machen (777), sowohl für Benutzer, Gruppe und Andere
     Plugin im wp-admin bereich aktivieren
     F5
     ????

163. Fr. Daniel on July 9, 2007 at 16:10 #

     Can someone clarify for me please?

     If I use this plugin to upgrade my site, does it delete ALL the files in the WP folders? For example, would it delete non-WP core files, such as plugin files that are placed in the admin folder?

     Thanks!

164. Martino on July 13, 2007 at 08:58 #

     Absolutely wonderful plugin =)

165. Martino on July 13, 2007 at 09:01 #

     This rocks. You rock. Thank you for sharing and helping people out. I send you a virtual beer

166. Ludwig Schuster on July 16, 2007 at 19:49 #

     Hallo, ich hab da ein großes Problem!

     Ich hab nach Anleitung installiert, und wenn ich dann unter Verwalten –> InstantUpgrade nachsehe, bekomme ich einen 404 error.

     Das ist auch nicht verwunderlich, weil offensichtlich der Link zum script falsch ist..
     dieser will das script unterhalb von wp-admin finden.

     Wo hab ich da nen Denkfehler, oder was hab ich falsch gemacht?

     Vielen Dank schon mal, grüße, und bis denn,
     Ludwig

167. Alex Günsche on July 18, 2007 at 08:32 #

     Ludwig, ich kann leider keine Funpic-Benutzer unterstützen, da die Funpic-Server eine ziemlich vermurkste Konfiguration haben.

168. John Baker on July 18, 2007 at 09:35 #

     Just to be sure. Will my site be secure if I use this plugin? Are the read/write permissions put back by the plugin, or are the left open?

169. Gary on July 29, 2007 at 04:41 #

     This is incredible! I am so grateful for this plug-in!

     There are a few things that I was worried about but lo and behold this worked like a dream! Here were my concerns:
     1) Will it overwrite changes I made to the default theme sidebar? NO!
     2) Will it overwrite changes I made to the header? NO!
     3) Will my advanced plug-ins still work? YES!
     4) Would it really reset the CHMOD’s? YES (the ones that matter anyway!)

     I am now a total fan!

     Thanks and Great Job!

     Gary

170. mark on July 31, 2007 at 02:34 #

     will this still function for someone that runs phpsuexec?

171. Alex Günsche on July 31, 2007 at 16:31 #

     Absolutely. You don’t even have to change permissions.

172. PJ on August 1, 2007 at 17:47 #

     I’ve had loads of problems when trying to upgrade my blog in the past, and had to revert back to the old version twice, but your plugin made it so easy to upgrade. Thanks so much!

173. Erich on August 3, 2007 at 08:08 #

     Herzlichen Dank für dieses Plugin. Bin begeistert. Hat super funktioniert!!
     Noch eine Frage:
     Die Schreibrecht bleiben auf 777, muss man diese nicht wieder zurücksetzen bis zum nächsten Upgrade?
     Sind meine Daten/Dateien noch sicher vor Hacker?
     Sorry für die Fragen, bin leider nicht so ein Profi.
     Danke und Gruss aus der Schweiz

174. 50+ Tools For The WordPress Admin on August 3, 2007 at 10:43 #

     […] Instant Update - Will handle the tedious chore of upgrading your WP install with just one-click. […]

175. tom on August 4, 2007 at 17:06 #

     I have the same problem as luca but I couldn’t find an answer here in the comments

     Fatal error: Call to undefined function current_user_can() in /home/wiredjes/public_html/wp-content/plugins/instantupgrade/admin.php on line 17

     I have installed the plugin, CHMOD adjusted, but the instant upgrade option doesn’t appear under manage and when I use the plugin shortcut, I get the fatal error message.

     Let me know what I need to do to correct the error. I’m using Wordpress 1.5.

176. Alex Günsche on August 5, 2007 at 09:53 #

     tom, the InstantUpgrade plugin requires WP 2.0 at least. Sorry, but you must upgrade from 1.5 to 2.0.x manually first.

177. Jeremy Clulow on August 6, 2007 at 11:49 #

     Thanks Alex,

     Definitely on my list of the 10 greatest WordPress plugins

     All the best,

     Jeremy
     www.webswonder.co.uk

178. mo on August 6, 2007 at 15:30 #

     Thank You for this excellent plugin, worked like a charm..

     just wondering though is there a program that changes chmod for all residing sub folders and files automatically?

179. Alex Günsche on August 6, 2007 at 19:11 #

     mo, this happens automatically: The InstantUpgrade plugin first removes all old files, then inserts the new ones, with an appropriate file mode.

180. kurt on August 7, 2007 at 02:17 #

     I’ve been using this plugin for months, and I have to say it is the greatest WP plugin ever!

181. Carl Mercier on August 7, 2007 at 13:58 #

     This is a great plugin! Thank you so much for it!

     One recommendation though, why doesn’t your plugin update itself automatically? And why not allow all my plugins to upgrade themselves?

     Plugin authors could put a simple XML file containing a version number, url of the latest revision in their plugin directory and instantupgrade could simply read that and upgrade if necessary.

182. LST on August 7, 2007 at 19:52 #

     There is a conflict with the WPG2 plugin. The instant upgrade plugin deletes the wpg2 files in the root folder of the wordpress installation. After upgrading the WPG2 plugin does not work any longer.

183. Alex Günsche on August 8, 2007 at 13:03