Polymathic

It seems like it would take a lot of work to get the in_place_editor to work in a partial on a collection, but it does. (It took me a lot of time to figure this out, but maybe I’m just more than average dense.) The best post to-date on this is at we eat bricks.

Just add the usual in the controller (user_controller.rb):

in_place_edit_for :user, :name

And, of course, the method:

def edit
  @users = User.find(:all)
end

Then, in the main view (edit.rhtml):

Nested resources in Ruby on Rails are sort of neat, but they are a pain to implement. What’s more, I have to ask myself, why bother?

If a resource has a unique identifier id, then why would you need to call its parent resource to call it? The unique identifier is enough. And what resource doesn’t have a unique id these days?

Geoffrey Grosenbach’s Ruby on Rails plugin calendar_helper is simple and easy to use. Maybe I’m just picky, but one part of it just wasn’t working right for me.

Originally, it looks like this on line 96:

cal << %(<caption class="#{options[:month_name_class]}"></caption><thead><tr><th colspan="7">#{Date::MONTHNAMES[options[:month]]}</th></tr><tr class="#{options[:day_name_class]}">)

It doesn’t really make sense for the month name to be in a TH tag and the caption to be empty. So, I put the …

If you want to move your Wordpress permalinks via 301, you can try to do it by hand using rewrites in your .htaccess file. Much easier is Dean’s Permalinks Migration Plugin for Wordpress.

On my work blog (http://www.synaxisworks.com/blog/), I used to use the default “?p=post-number” format, and I wanted to change to a more SEO-friendly format. I setup Dean’s plugin. The first problem is that I didn’t know what to put for the “old permalink structure”. I tried a million combinations of text, regex, and Wordpress codes to try to get it to match the …