É agora sempre uma Estadia boa para promover Wordpress
Fevereiro 8o, 2008 · por David Bradley
Eu promovi finalmente meu local de Sciencebase à versão a mais atrasada de Wordpress, languishing na versão 2.1.3 para distante demasiado longo e houve muitos melhoramentos da segurança entre essa versão do legacy e a versão atual 2.3.3. Era um borne por Wayne Liew no nomeado inteligente COM do ponto de Wayne Liew isso persuadiu-me fazer o necessário.
Liew indica que promover à versão a mais recente de Wordpress pode ajudar proteger seu local das falhas de segurança menores. Por exemplo, o melhoramento 2.3.2 a 2.3.3 recente é requerido simplesmente porque circumvents um problema da segurança por que registaram usuários podem editar os bornes de outros usuários', que não é obviamente uma coisa boa. Mesmo que o único melhoramento da lima vale a pena fazer se impedir alguém que corta seu local.
Liew recomenda fortemente usar o melhoramento automático de Wordpress Plugin (WPAU) mas mim deve dizer que era com trepidation que eu investiguei como fácil um melhoramento de uma versão tão velha seria feito manualmente ou automatizado.
Eu tinha promovido manualmente de uma versão 1.5 ou dos thereabouts e tinha-a encontrado para ser rather doloroso nos termos do revestimento protetor - acima das limas, suprimindo limas velhas e os dobradores, recordando que a não suprimir, restaurando as permissões etc. etc. da lima, assim que me tempted muito usar WPAU.
As partes traseiras plugin - acima de suas limas e a base de dados, desativam encaixes, downloads o melhoramento de Wordpress arquivam-nos, instalam-n, reactivates somente aqueles encaixes que foram desativados, limpam acima das limas provisórias e dos pontos você da “à ligação final do melhoramento base de dados” em Wordpress que recarrega seu local.

Está aqui uma ponta rápida para aquelas que querem promover - tente WPAU em um local menor, mais menos importante primeiramente. Se todo trabalhar perfeitamente então dar-lhe-á a confiança para empreender um melhoramento automatizado em seu local principal.
A ponta aplica-se obviamente somente se você tiver mais de um local, e se um deles for mais menos importante para você do que o outro. Meu melhoramento bem sucedido do local menor (albeit somente saltando 2.3.2 2.3.3) convenceu-me que e assim que eu empreendi um melhoramento de Sciencebase WPAU.
Naturalmente, se você estiver em um anfitrião com o sistema de Fantastico você automatizou os melhoramentos de Wordpress construídos dentro. O único problema é que Fantastico se retarda geralmente atrás da liberação atual (na altura da escrita, se está sentando em 2.3.2, no fato)

Em todo o caso, WPAU trabalhou perfeitamente, a primeira vez, que era um relevo surpreendente. 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