Atom feed
While I’m in the posting mood… As of a month ago I have a shiny new Atom feed. (that my previous post broke momentarily ): Update your aggregates, or not, the RSS version still works.
Here’s the beautiful haml that made it
While I’m in the posting mood… As of a month ago I have a shiny new Atom feed. (that my previous post broke momentarily ): Update your aggregates, or not, the RSS version still works.
Here’s the beautiful haml that made it
Been a while… So my blog was broken just now, not sure for how long. Not more than a month I think. The problem was in the acts_as_taggable plugin, which rumor has it is dead. For now I will still use it, and describe the fix in case it also is broken for you.
The problem is in the join table. The geniuses decided to make the join table <tag class><taggable class>. This is backwards from the regular has_and_belongs_to_many convention in activerecord. Somewhere, somehow, this backwardsness was reversed. I had it using it’s default join table before (tags_posts) and it broke as now it’s looking for poststags. So I add an option to the call:
acts_as_taggable :join_table => :tags_posts
I suppose I could have changed the table name, but at least this way it will never (hopefully) break again. I’m not quite sure how this default behavior changed in the first place.
Well, I finally did it. I have comments now. Stop on by and drop one in!
I use darcs in my rails apps. The combination of the generator creating several files at a time and not including the logs in the repo makes adding the new files cumbersome after a generate.
No worries! Just add ^log(/|$) to the _darcs/prefs/boring file. Now you can darcs add -r * after generates and rest easy.
There it is! I got the rss up and running. http://von.fugal.net/blog/rss gives you a nice feed of the 10 most recent entries. You can also get a topic-wise feed by simply adding /
Next task, fix the design!