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
