Gang Aft Agley

I verified that the file created in textmate was a textile entry, though upon saving it it changed to a markdown with smartypants filtered entry.

At this point I have gone into the admin and verified that textile is the preferred filter. This entry is being created through the admin interface to isolate the error, either in backend or the content controller.

I’ve just upgraded to the latest, greatest rev. 1175 and noticed that my last post, although Textile is the default filter se t in the admin, the post was sent as markdown smartypants. Not sure if I hit the wrong keys in textmate, or if its an actual bug. So this post is jsut the follow up to duplicate the error.

So I’ve noticed that the site seems to be having some problems staying afloat. I believe it is happening in the archives sidebar plugin, as that hasn’t been displaying for a while, and it should be.

The route to the articles still works its just the sidebar that isn’t working. More later as I dig further.

Forced onto outlook by corporate beauracracy, I spend my day trying to make intelligent rules to filter mail here and there so that I can minimize the amount of time it takes to handle looking at my new emails.

Run Rules Now

I migrated to latest typo version yesterday, and had no problems with it until tonight. When I went to login just a few minutes ago typo kept telling me that my login was unsuccessful.

$ ./script/console production
Loading production environment.

you = User.find_by_login('yourusername')

=> #<User:0x8f8baa4 @attributes={"name"=>"yourusername", "id"=>"1",........

you.password = you.password_confirmation = 'newpassword'

=> "newpassword"

you.save

=> true

quit

Using this I was able to reset my password back to its original value, and the fact that I’m posting this shows that it worked.