8:05a.m. CMS Woes

So, Rails is now at 1.1 Yay for rails! Except.

I haven’t been able to update Typo in months, and according to some messages in the Typo mailing list, Rails 1.1 breaks Typo.

I’m not sure what to do about any of this. I could figure out how to have Typo just run on it’s own version of rails, separate from my host’s version (they’re updating to rails 1.1 any day now). However, then I’m stuck there with my own version of rails and Typo, and may make it difficult to ever get passed that point.

Plus, I have this huge Abnormal Psychology test tomorrow. So I can’t really worry about weather or not my blog exists tomorrow.

What sucks is that I really like rails and Typo. I love Typo. The problem is, its just in too much flux, and its too difficult to keep it current. So I’m not totally sure what I’m going to do yet… for now, I’m going to attempt at freezing my version of rails as to prevent my blog from being totally broken until I can deal with starting with Typo fresh/attempting to update my version of Typo and rails/ or move to another CMS. There is no such thing as the perfect CMS. Not even close. So, we’ll see, we’ll see.