search for: rails_acts_as_t

Okay, so I just realized there seems to be two acts_as_taggable modules, the gem and the plugin 1. which came first? 2. what''s the difference? (internals, not ones a gem and ones a plugin) 3. which one is better? ;-) -- Craig Beck http://www.luckybonza.com AIM: kreiggers

I was reading rails recipes and it shows how to use acts_as_taggable with only 2 tables, a tags and a taggings table. But I think that its related to an older acts_as_taggable version because now it seems that it works with one tags table and one taggings table for each tagable model, like this: tags photos tags_photos Which means I need one new table for each model I want to tag.

I installed the acts_as_taggable plugin that DHH wrote. Now I have met problems on using it: class Book < ActiveRecord::Base acts_as_taggable end mybook = Book.new mybook.tag_with(''red library book'') But the system tell the wrong message: undefined method `parse'' for Tag:Class d:/ruby/lib/ruby/gems/1.8/gems/activerecord-1.14.0/lib/active_record/base.rb:1123:in

I''ve been contemplating the utilization of "tags" functionality for categorizing records in my application. For example, a record can have any tag associated with them: volunteer, donor, phone_caller, etc. (Much like delicious) Has anyone already laid out a good architecture for implementing this on the DB, or other medium? I''m sure I can custom build something, but

I have gotten acts_as_taggable to work for a test application as documented on taggable.rubyforge.org I am following Chad''s excellent examples in ROR Recipes Beta book. I have a few questions and hope that Chad or some other expert can help clarify them. 1. Why is the book suggesting to use taggings table instead of tags_contacts, as mentioned on taggable.rubyforge.org?