Updating WordPress
Keep WordPress updated! New features come out and you want them. Bug fixes come out and you want them. Security fixes come out and you really want them.
WordPress offers automatic updates, or your host my do it for you. Find out how it works with your specific host and do it whenever there is an update!
Updating Your Plugins
keep an eye out for this
find the upgrade area under tools
you can upgrade all your plugins at once
Updating WPFolio
Keep an eye out in your WordPress Administration Panel for updates to WPFolio as well as on this site. And install the updates!
Backing Up
Look, there’s plenty of information on how to back up WordPress on the Codex and plenty of horror stories – I’m just saying do it, do it regularly, and automate the process. You worked hard setting this up. Keep a backup just in case. Plugins are available to help and your host (Dreamhost is great for this) may keep regular backups as well – but don’t depend on them. Make sure you keep your own backups.
Loading ...
10 Comments
Hi, I use WPFolio for the website of the arts non-profit I coordinate. I don’t have much knowledge on WordPress or websites, but have worked on the site anyway. I did some customization so that the site meets our needs, and would like to know if I’ll miss these customizations if I update the theme. We’re using now version 1.4.1. Besides this, I’d like to know if it’s safe to update WordPress to 3.0 using WPFolio 1.4.1. Many thanks.
Carlos, good question.
It depends on if you modified the css or php files in the theme. If your customization was with the widgets and theme options, then yes, they should remain.
If you did modify the css or phpop files, then your changes would be lost if you overwrote the theme with an update. You would have to cherry-pick out your changes and rewrite them into the new files. However, there is a better way and I just posted a new page on the site about Child Themes which may be helpful for the future.
As far as I know, it should be fine to update to WordPress 3.0 though the 1.4.1 version doesn’t take advantage of all the features, of course.
Steve, thanks for the quick reply. As an amateur, sometimes I don’t keep track of the changes I make…
But I’ve made changes in css and php files.
I think I’ll have to first compare the original 1.4.1 files with the current ones, keep tracks of the changes made, then update and rewrite the changes. Can you suggest any different path? Also: I think of first updating WordPress to 3.0 and then updating WPFolio. Or should I do the opposite?
Thanks again.
Yeah, it’s always good to comment your code so you can know what you did when looking back.
I don’t think it matters if you update WP or WPFolio first.
Definitely back up your work. I would make a child theme with the changes you know know you made and see how it works. But yeah, you will have to comb through and look.
Also, if WPFolio has been useful to you, please consider donating. Thanks!
Steve, thanks again. And definitely WPFolio is very useful and will consider a donation as soon as possible. However, as a non-profit we’re still struggling with donors’ retraction since last year, due to the overall financial crisis.
But we’ll do it as soon as we can.
Hi
I just loaded your update and now i cant access my site at all.
The url comes up blank, not as an error just blank
please help, it said the ‘maintenance was complete, and the new version was updated)
regards
That sounds frustrating. My best guess is that something happened during the update. Because I’ve tested the theme on several installs, it doesn’t include any major changes from the last version, and it made it through the official WordPress theme testing process, I’m suspecting it’s related to something else. Search online and see what you can learn. If that doesn’t work, post on the WordPress forums. If you want it taken care of immediately, I would put it on WPQuestions. They are surprisingly fast.
Thank you
will try the WPquestions as i need it resolved asap
regards
Georgina
Turns out it may have been my mistake after all, but I can’t be sure, check here
It turns out there was a problem, see more here.