upgrading typo to 2.5.6
Well! I upgraded my ooooold (2.0.6) Typo install to the spiffing new 2.5.6. I learned all about rake migrate
(which didn’t want to work) and such fun things. And, because of the new theme engine, I’m back to square one, visually speaking. And my other preferences are gone, too.
Upgrading your Typo is as easy as this:
- Download the new Typo to a directory on your server (the one where your domain points, ideally)
- Edit the database.yml file to reflect your current database settings
- Stop the web server (or just the FCGI process, if you can—but it mustn’t be allowed to respawn)
- In the new, decompressed Typo directory, run
rake migrate
- If it fails, check your version with
rake --version
—if it’s 0.6.0, upgrade usinggem update rake
and wait. And wait. And wait some more, because Rubygems is sluggardly. Then try again.
When rake migrate
is working, the results will look like:
Processing 35 articles Linking article authors to users Processing 35 articles Processing 13 categories Adding GUID to articles
But you’re not quite done:
- Back up your old Typo directory—I did
mv typo typo_bak
- Rename your new Typo directory from
typo-2.5.6
to the same name as your main Typo dir was before - Restart your web server/FCGI process
And, behold! Your upgraded Typo installation, complete with utterly vanilla default theme Azure. Le sigh. Well, I have a new design ready and rarin’ to go, I guess I just have to find the time to HTMLize it now.
This wouldn’t also happen to work if you want to go from 2.5.6 to the trunk, would it? Cause whatever is going on with the migrations just doesn’t want to work…
Just make sure you include a flower in your new layout.
I almost thought I was here: http://blog.curthibbs.us/
rumred, maybe I should have titled the post "design your blog software!" 🙂
Back to the ol’ flowers for the time being. It was faster than doing my new one. I am tres lazy.
Thanks, too bad 2.0.6 -> svn trunk wasn’t this easy…
I use Firefox in Ubuntu!
Well at last catched the problem!
I’m working!
Thats correct!
I was very dissapointed of this.
Thanks for taking the time to do it 🙁
That’s awesome 🙁
Thanks for the write-up.
Well at last catched the problem…
Thanks for the write-up.
Good idea 🙂
Thanks for taking the time to do it 🙂