Still need to fix the overflow situation there dimitry ;)

Something to consider should be the existence of a duplicate post. Perhaps add something to your protected method ;)

Joel: Good points and something to think about.

› I’ll fix overflow tomorrow hah. Keep forgetting about it.

› As far as duplicate posts, I never even thought of that b/c my blog is so damn small so far. In the future though this may be a problem.

I need to sleep on this (so so late here) and think of a nice sql-effective solution :)

John Gruber wrote about permalink design a little bit in one of his articles,

http://daringfireball.net/2007/03/blank_slate

I think one thing you might want to consider is adding in the option to override the default permalink so that if a title is unusually long, the URL doesn’t have to be as well. As John wrote in his article,

“Long titles can be amusing; long URLs are simply annoying.”

Jason: Thanks for sharing that link. In my backend I usually save a post in draft mode (for proof-reading, check if permalink is awkward or too long) then Publish it.

That is a good addition though (max length) and will have to add it.

Hi guys,

What do you think of this solution: http://www.notsostupid.com/blog/2006/07/07/urls-on-rails/

Could be a nice alternative.

This is a nice solution, but I wonder if its overkill. Once you have

@post = Post.new(params[:post])

you should be able to interact with the title to do

@post.title.gsub!!.downcase!!(/\ +/, ’-’)

and everything will be done in place.

Of course, someone brought up the fact that you might want to edit the permalink, which is easy enough to allow through Javascript. First you’d have to track whether the permalink had been changed. If it had not, the onchange event for the title should update the permalink. Then you can just save it along with your post the first time.

Edit: a bug in your comment text processing caused the !! to be removed in the code – doubling them up fixed it.

I think the implementation could be any way you find it convenient (and efficient). The thing I couldn’t find is the actual RegEx (yet it looks simple enough).

The more I think about it, the more I like the Javascript solution to generating permalinks.

No it didn’t, and Textile killed part of the code. Let’s try again:

@post = Post.new(params[:post])
@post.title.gsub!(/\W+/, ' ').strip!.downcase!.gsub!(/\ +/, '-')
if @post.save
    #...
end

Nice writeup Dimitry, what happens if someone edits the title of a post, should it re-generate the slug-url? Or does that defeat the purpose?

Currently I have an id value included in the url, and the slug value as well, and always just find by the id.. so the slug value can be modified without breaking the user-experience..

Nice site too, is it RoR?

Word Up – Releod (TR42)

Adam: On edit, I simply add another textarea with the slug, kinda how WordPress does it.

That’s interesting about using post id along with the slug. In my case, I save posts in draft and edit them pretty good (title, body, etc.) so by the time I publish it, the title will most likely not change.

But that’s just my personal system (and yup, site’s in RoR)

Nice work Dimitry, the site looks ace!

Where are you hosting it?

-

For me, I have the slug generated anytime the entry is created,saved,etc. Keep the users updating the website away from that type of thing.. but I guess for your own site you can trust yourself, haha.