Home Page dei Figs di Sig Newsfeed dei Figs di Sig Figs di Sig dal email Figs di Sig la maggior parte dei alberini popolari
Figure significative
Assistenza voi, aiutandosi con blogging, la lettura rapida e le punte di tecnologia

← Il mito di Feedburner SQT: Per mezzo di un registratore di voce dell'aria →

Ora è sempre buon Time per aggiornare Wordpress

8 febbraio 2008 · da David Bradley

Marchio di WordpressInfine ho aggiornato il mio luogo di Sciencebase all'ultima versione di Wordpress, languishing alla versione 2.1.3 per lontano troppo lungo e ci sono stati molti aggiornamenti di sicurezza fra quella versione dell'eredità e la versione corrente 2.3.3. Era un alberino da Wayne Liew sul chiamato intelligente COM del puntino del Wayne Liew quello lo ha persuaso di fare il necessario.

Liew precisa che aggiornare alla versione più recente di Wordpress può contribuire a proteggere il vostro luogo dai difetti di sicurezza secondari. Per esempio, l'aggiornamento recente 2.3.2 - 2.3.3 è richiesto semplicemente perché aggira un problema di sicurezza da cui hanno registrato gli utenti possono pubblicare gli alberini di altri utenti', che non è ovviamente una buona cosa. Anche che il singolo aggiornamento della lima vale la pena di fare se evita qualcuno che incide il vostro luogo.

Liew suggerisce vivamente usando l'aggiornamento automatico di Wordpress Plugin (WPAU) ma io deve dire che era con il trepidation che ho studiato quanto facile un aggiornamento da così vecchia versione sarebbe fatto manualmente o è stato automatizzato.

Avevo aggiornato manualmente da una versione 1.5 o dai thereabouts e la avevo trovata per essere piuttosto doloroso in termini di lime sostenenti, cancellando le vecchie lime ed i dispositivi di piegatura, ricordantemi quali per non cancellare, ripristinandolo i permessi ecc ecc della lima, in modo da molto è stato tentato di usare WPAU.

Il plugin sostiene le vostre lime e base di dati, disattiva i collegamenti, trasferisce l'aggiornamento dal sistema centrale verso i satelliti di Wordpress li archivia, installa, riattiva soltanto quei collegamenti che sono stati disattivati, pulisce le lime provvisorie ed i punti voi “al collegamento finale di aggiornamento della base di dati„ in Wordpress che reboots il vostro luogo.

Aggiornamento automatico di Wordpress

Qui è una punta rapida per quelle che desiderano aggiornare - provi WPAU su un più piccolo, luogo meno importante in primo luogo. Se tutto funziona perfettamente allora gli darà la riservatezza per intraprendere un aggiornamento automatizzato sul vostro luogo principale.

La punta si applica ovviamente soltanto se avete più di un luogo e se uno di loro è meno importante voi che l'altro. Il mio aggiornamento riuscito di più piccolo luogo (anche se soltanto saltando 2.3.2 - 2.3.3) lo ha convinto che ed in modo da ho intrapreso un aggiornamento di Sciencebase WPAU.

Naturalmente, se siete su un ospite con il sistema di Fantastico avete automatizzato gli aggiornamenti di Wordpress sviluppati poll. L'unico problema è che Fantastico si ritarda solitamente dietro il rilascio corrente (ai tempi della scrittura, sta sedendosi a 2.3.2, in effetti)

Screenshot di Sciencebase

In ogni modo, WPAU ha funzionato perfettamente, prima volta, che era un rilievo stupefacente. However, having been using a 2.1.5 widgetized system the final result was a messed up sidebar that took a few little tweaks to fix (some widgets were missing and others were in the incorrect order, although that may have been down to caching problems rather than the upgrade itself).

However, one or two plugins simply failed to run in the latest version (Top Posts by Category and Get Recent Comments, for instance). I removed these altogether pending the release of compatible updates. Other than that I’ve had no problems. Several other plugins were flagged as requiring upgrades, and these were duly done. If you happen to visit Sciencebase.com and spot any problems I’ve not seen, perhaps you could let me know.

Next week: How to Steal a Wordpress Theme. Subscribe to the Sig Figs feed to be alerted.

13 responses so far ↓

  • Animati // Feb 11, 2008 at 3:40 am

    Thank you for well-timed prompt! I’ll update my wordpress-based photoblog today.

    Animati’s last blog post..Bee Gee’s Yawn

  • David Bradley // Feb 12, 2008 at 2:00 pm

    Although Sig Figs was at version 2.3.2 of Wordpress and it would have been simpler just to download the single file update required to take it to 2.3.3, I thought I’d better stand by my assertions in this post and use WPAU. It worked (eventually). I had to do several page refreshes during the automated update. And, although everything was fine in the end, I can see that some users might panic and think they’ve trashed their site when they see blank screens. Don’t panic. Just do a full refresh of the page at whatever stage it stalls at, and repeat until you get the link to move on to the next step.

    db

  • Deborah // Feb 14, 2008 at 12:50 am

    David,

    I was glad to hear your good news about upgrading WordPress with this plugin. Like you, I was very concerned about upgrading. I used the plugin, and it worked, but I could not download the backup files.

    While I’m glad the upgrade worked (at least I think it worked! I’m still checking the pages), I was very disappointed that it did not allow me to download the backup files.

    Each time I tried to download, all I got was a page not found error. I checked the files online to see if they were on my site, but couldn’t find the backup files. All I found in the wpau-backup folder were an empty index.php and an empty index.html file, with no content.

  • David Bradley // Feb 14, 2008 at 8:08 am

    Deborah, if it worked, then it doesn’t matter about the backup files (this time). Next time do a manual backup before you run the plugin, just in case the same thing happens again. Your blog is definitely showing the latest version, right?

    db

  • David Bradley // Feb 14, 2008 at 9:17 am

    Wordpress version 2.5 is on its way. In fact, you can trial it now http://wp.chrisjohnston.org/?p=3

    db

  • Deborah // Feb 14, 2008 at 12:35 pm

    Hi David,

    Being the cautious person I am, I did do a backup before I ran the plugin. I was glad it worked! But a bit concerned that the plugin’s backup didn’t work.

    Yes, the site I used this on has been updated correctly and is showing the most recent version.

  • David Bradley // Feb 14, 2008 at 1:52 pm

    Deborah, it worked fine on the various blogs I ran it on. I guess we’ll never know why you couldn’t get the backups within the plugin itself…

    …as with all plugins there could be a conflict with another plugin. Maybe the way to do it next time would be to deactivate all plugins manually except WPUA, and then reactivate once everything is complete. I realize that’s starting to negate some of the benefits of WPUA, but it would still make the upgrade process simpler than a total manual upgrade.

    db

  • Deborah // Feb 15, 2008 at 2:29 am

    Brian,

    Good suggestion. I’ll turn off the plugins the next time, before I use the upgrade plugin. Hopefully I’ll remember to come back and report if it worked any better!

  • David Bradley // Feb 15, 2008 at 7:30 am

    Deborah…who’s Brian?

    Yes, please do, this is likely to be an ongoing thread especially as Wordpress 2.5 is on its way next month.

    db

  • Deborah // Mar 29, 2008 at 1:10 am

    Hi David,

    Not sure where I found the name David. My apologies!

    I read a review of WordPress 2.5 earlier today. If this gets through (I wasn’t sure if you accepted urls in your comments) - here’s the site:

    http://tinyurl.com/2s8g6j

  • David Bradley // Apr 1, 2008 at 3:06 pm

    Well as most Wordpress bloggers will know by now, the program has reached version 2.5 and it’s soooo much slicker and better than the previous versions, so now really is the time to upgrade. Double check your backups, make sure you know which plugins will fail and take the plunge!

    db

  • Gaida // Apr 10, 2008 at 3:01 am

    Hi David,
    Thanks for your detailed post on the importance of upgrading wordpress.

    I must admit I was lagging with my upgrades & was very wary about doing it. Thankfully all went well. Haven’t taken the jump to 2.5 as yet.

    I’d also heard about deactivating your plugins before upgrading even with the WPAU. I have noticed that a link has appeared informing me there is an upgrade.

    Gaida’s last blog post..Understanding Motivation

  • David Bradley // Apr 10, 2008 at 7:42 am

    Deactivating plugins is an essential, but with WPAU it reactivates only those that were active before the upgrade so any disabled plugins that happen to be in your folder don’t get inadvertently started. Jump to 2.5, security and features make it a must. 2.6 is on its way soon, though…

    db

Leave a Comment

Comments are checked for spam before appearing, no need to post it twice.

Related Posts