Yet Another Typo Upgrade, Yet Another Trip to the MySQL Admin Page
I just upgraded this blog to Typo-5.1.3. Here's a short description of the two night escapade that was. I install typo (copying the database.yml and other configs) and point the symbolic link I have for the domain to it, everything stops working. Fine, I know they probably updated some tables so I wasn't expecting that to work. So I run:
$ rake db:migrate
Thinking that will fix it. Nope. That doesn't even run. Why? Well there were lots of errors and what-not but after some research and having to read the code, I found out that Typo-5.1.3 thought I had to have a frozen version of Rails in my vendor/rails. However, I just installed it, so of course I don't. So I get rid of vendor/rails:
$ rm -rf vendor/rails
Now I run:
$ rake db:migrate
And failure. After some more reading I learn that Dreamhost decided to update itself to Rails 2.1.0 which is, of course, incompatible with this version of Typo. Great. Now I do have to have a frozen version of Rails. Now I have my own gems on Dreamhost, so I think, no problem, I'll just move it over to that.
$ rails -v Rails 2.1.0
Great, it's not even in my gems. So I wget all the Rails 2.0.2 parts (remember the Ruby-Killer on Dreamhost will stop any remote fetches gems!). I install Rails 2.0.2 into my local gems.
$ rake rails:freeze:gems
Still fails. Great. Turns out Dreamhost installed Passenger for Rais, which is great since it'll speed up loading. However it's also not working with Rails 2.1.0, which is fine I think since I froze it, but it turns out that Passenger ignores your Gems. Awesome. So I try locking the RAILS_GEM_VERISON and the ENV['GEM_PATH'] in environment.rb and then it works. Now, I try to access the new /admin page. That works. Now we migrate.
$ rake rb:migrate
Failed in Version 71. F**k! I go to the MySQL Admin page with a righteous fury and open the migrate script up to see what the 071 script does. Looks like it just makes the tag names safe by converting '.' to '-'. Awesome. Now why would that fail? Who knows. I look through tags and I don't even have any with '.' in them. Great. I do have some with ',' in them, so I fix those and move the schema_info table to 71. I run the migrate again and it seems happy since 71 is the latest. Now I load the front page of the blog.
Fail. I'm fairly peeved now.
I decide to heed previous experience here and go through the Admin pages one by one and which ones fail. Sidebar. That old f**ker. I go into the MySQL Admin and save the old sidebars in a text file and rip them all out. Reload Admin page. Works. Reload blog. Works. Great! Finally. Easy install huh? You just have to hack you database, edit a bunch of config files, and burrow through some code to get it working. At least I can use the /admin page to edit posts again.
