Why my Typo is still busted
It seems that the reason my Typo install has been busted for so long on DH here, is that during some database migration in the past DH's ruthless ruby killer decided that I shouldn't be taking so long in updating my database and killed the process, but somehow upped the migration number. When I went through the database by hand and checked all the tables it became clear very quickly that this had been the case. My tables were severely out of date. Several had multiple fields missing or mis-sized. Once I added/modified these tables everything seems to be running smoother. This brings up another problem.
Here's an exercise for the reader: Why the heck doesn't Rails/Typo report such an error? (Missing fields in the database)
Update: Well, I said it's more stable, but what does it do as soon as I tried to post? Crash! 500! I'm posting this from the phpMyAdmin interface now. Where did Web 2.0 go wrong?
arg.
Update: After running a manual sweep of the tmp/cache directory (DH would kill any rake task trying to do so), my blog became again, more responsive. I'll have to add a cronjob to clean it out manually every night.
Update: Here's my new nightly regiment:
rake tmp:clear rake tmp:create rake sweep_cache rake db:sessions:clear rake log:clear
Clownfish Resting in an Anenome in Oil
File does not exist: .
Typo 4.1.1 Sidebar is busted
Update: I've found that I can get to a semi-stable point by doing the following:
cd $YOUR_TYPO_DIR
rake -f Rakefile sweep_cache
rake -f Rakefile tmp:clear
killall -USR1 /usr/bin/ruby1.8
killall -USR1 /usr/bin/ruby
Then goto your admin/sidebar interface and add/delete/modify your entry. Hit "Publish" and it should work. However, if you change something and hit it again, it will fail. You'll have to reload the page so that the "Changes Published" (i.e. the flash) is empty.
Typo Issues
rake db:migrate
I'd wait and wait and wait while the process grew past 100MB and then got the axe. I futzed around with re-running the rake task, trying to find the task manually and finally I started to get frustrated with the whole thing and I had decided to move to Mephisto, another Rails app, but it's more of a CMS than just a blog. I might still move, since they have a blog post converter, but it's only somewhat maintained by it's developers at the moment, and I certainly don't have the time to develop it further. Eventually I deleted some of my older typo installs, installed the typo-4.1.1 version, restored the MySQL database (I managed to completely screw up that thing by manually deleting the session table), ran the rake migration command with the exact rakefile I meant to use
rake -f Rakefile db:migrate
(perhaps the others were spidering all the rakefiles it could find in parent and sibling directories), and letting it "sit" for a while (originally after I had done all of that, it was failing to get to the admin console because it couldn't find the blog with "blog_id==4", which I don't have), then I could log in and everything starting working normally. I think the lesson here is to stay on the stable release branch. Having a host with a backup of your databases is really nice too.
An odd series of crappy happenstance. Part Deux.
Update: Amber corrected some times/dates for me.
The Big 5-0
Storm Damage
Weight Loss Update
McConkey's Run
File does not exist: .
Here's a view from below of McConkey's Run. This is a double black diamond run at Park City in Utah. I think that most other resorts would classify this as a black diamond, but it was still rather hard.
Update: I just updated the blog here to the most stable version of Typo (rev 1256) so the layout of the image to the right here is a little weird. It seems to overlap the post instead of leting the post flow around it.
On a different note, it seems that the vacation caused a bit of a setback on the diet program. Just before the trip I was at the 40lbs mark, now, well, subtract 2.2lbs to that.
