Thanks Bruno, thats exactly what I needed. On a similar note, my site
is now returning undefined method 'related_tags'. It seems like it is
not looking into the tag model in the community engine plugin where
said method is located. Could this be a problem with desert? I tried
creating a tag.rb file in my app/models directory to try and lead
rails to the correct file but that didn't work. Any ideas?

p.s. Thanks for all the help everyone, I know I ask a ton of
questions:)

On Jul 28, 10:34 am, Bruno Bornsztein <[email protected]>
wrote:
> This line, in ce/app/models/tag.rb:
>
> require_dependency File.dirname(__FILE__) +
> '/../../plugins/acts_as_taggable_on_steroids/lib/tag.rb'
>
> Just requires the tag model from the taggable_on_steroids plugin, and adds
> some methods to the class.
>
>
>
> On Mon, Jul 26, 2010 at 7:13 PM, Edward Funger <[email protected]> wrote:
> > I've been working on integrating the acts_as_taggable_on plugin into
> > community engine. I'm running into a problem where Tag refers to the
> > model tag.rb that was previously in the acts_as_taggable_on_steroids
> > plugin. Does anyone have an idea as to what is going on?
>
> > On Jul 22, 7:23 am, Bruno Bornsztein <[email protected]>
> > wrote:
> > > If you're really enterprising, you could swap in acts_as_taggable_on for
> > > acts_as_taggable_on_steroids in the CE plugins folder, and integrate it
> > into
> > > the app (with passing tests, of course). I'd happily accept that change
> > into
> > > core.
>
> > > Thanks,
> > > Bruno
>
> > > On Thu, Jul 22, 2010 at 9:20 AM, shiftshane <[email protected]>
> > wrote:
> > > > Edward,
>
> > > > Acts_as_taggable_on supports "context" tagging, which sounds very much
> > > > like you're after. Perhaps you want to dissect that and figure out how
> > > > they have it working. Also, i really don't think it would be too hard
> > > > to just drop that plugin in over AATOS. It should work out of the box
> > > > with just a couple column additions to one of the tables.
>
> > > >http://github.com/mbleigh/acts-as-taggable-on
>
> > > > Shane
>
> > > > On Jul 21, 11:37 pm, Jim Ruther Nill <[email protected]> wrote:
> > > > > hmm.  I think you can override the tag_list getter and setter methods
> > so
> > > > > that you can add tags like
>
> > > > > microsoft - company, campus - location
>
> > > > > here's a pseudo code for the setter and getter
>
> > > > > def tag_list=(tag_names)
> > > > >   temp = []
> > > > >   tn = tag_names.split(',')
> > > > >   tn.each do |t|
> > > > >     main_tag = t.split(' - ').last
> > > > >     description_tag = (t.split(' - ') - [main_tag]).join
> > > > >     # collect all main_tag and write_attribute them to tag_list
> > > > >   end
> > > > > end
>
> > > > > def tag_list
> > > > >   #collect the tags and [main_tag, description_tag].join
> > > > > end
>
> > > > > hope this can help you in some way.
>
> > > > > On Thu, Jul 22, 2010 at 3:29 AM, Edward Funger <[email protected]>
> > > > wrote:
> > > > > > Sorry, just came back to this post and realized it wasn't very
> > clear.
> > > > > > What I would like to do is have each tag have a descriptor that
> > > > > > specifies what aspect of the object it is tagging. For example, if
> > I
> > > > > > have a model Interview, I would like to be able to tag the
> > interview
> > > > > > multiple times with tags (in the form (name,descriptor))
> > ("microsoft",
> > > > > > "company"), ("campus", "location"). The problem now is that I can
> > only
> > > > > > tag said model as ("microsoft") and ("campus"). I would like to do
> > > > > > this because I don't want to hardcode fields into my model, so that
> > > > > > the end-user can add or remove fields through an interface on the
> > > > > > front-end. I'm not sure if it is worth mucking up the
> > > > > > acts_as_taggable_on_steroids plugin though. Does anyone have any
> > > > > > ideas?
>
> > > > > > On Jul 21, 10:41 am, Edward Funger <[email protected]> wrote:
> > > > > > > I would like each tag to also have a type(name it something
> > different
> > > > > > > than type) so that the tags are searchable and addable by their
> > name
> > > > > > > +type.
>
> > > > > > > On Jul 20, 8:42 pm, Jim Ruther Nill <[email protected]> wrote:
>
> > > > > > > > it's fine if you want to add another field.  and with desert,
> > you
> > > > can
> > > > > > just
> > > > > > > > copy the tag.rb file to your app's model directory and modify
> > it
> > > > there
> > > > > > for
> > > > > > > > whatever functionality you want to add.  may i ask what you
> > want to
> > > > add
> > > > > > to
> > > > > > > > the plugin?
>
> > > > > > > > On Wed, Jul 21, 2010 at 7:52 AM, Edward Funger <
> > [email protected]
>
> > > > > > wrote:
> > > > > > > > > I am trying to figure out a way that I can continue using the
> > > > > > > > > acts_as_taggable_on_steroids plugin but I want to add another
> > > > column
> > > > > > > > > to the tag.rb model. Am I going to start from scratch and
> > build
> > > > my
> > > > > > own
> > > > > > > > > tagging system or would it be easier to modify the plugin?
>
> > > > > > > > > --
> > > > > > > > > You received this message because you are subscribed to the
> > > > Google
> > > > > > Groups
> > > > > > > > > "CommunityEngine" group.
> > > > > > > > > To post to this group, send email to
> > > > > > [email protected].
> > > > > > > > > To unsubscribe from this group, send email to
> > > > > > > > > [email protected]<communityengine%2Bunsubscribe@
> > > > > > > > >  googlegroups.com>
> > <communityengine%2Bunsubscribe@ googlegroups.com>
> > > > <communityengine%2Bunsubscribe@ googlegroups.com>
> > > > > > <communityengine%2Bunsubscribe@ googlegroups.com>
> > > > > > > > > .
> > > > > > > > > For more options, visit this group at
> > > > > > > > >http://groups.google.com/group/communityengine?hl=en.
>
> > > > > > > > --
> > > > > > > > -------------------------------------------------------------
> > > > > > > > visit my blog athttp://jimlabs.heroku.com
>
> > > > > > --
> > > > > > You received this message because you are subscribed to the Google
> > > > Groups
> > > > > > "CommunityEngine" group.
> > > > > > To post to this group, send email to
> > [email protected].
> > > > > > To unsubscribe from this group, send email to
> > > > > > [email protected]<communityengine%2Bunsubscribe@
> > > > > >  googlegroups.com>
> > <communityengine%2Bunsubscribe@ googlegroups.com>
> > > > <communityengine%2Bunsubscribe@ googlegroups.com>
> > > > > > .
> > > > > > For more options, visit this group at
> > > > > >http://groups.google.com/group/communityengine?hl=en.
>
> > > > > --
> > > > > -------------------------------------------------------------
> > > > > visit my blog athttp://jimlabs.heroku.com
>
> > > > --
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "CommunityEngine" group.
> > > > To post to this group, send email to [email protected].
> > > > To unsubscribe from this group, send email to
> > > > [email protected]<communityengine%2Bunsubscribe@
> > > >  googlegroups.com>
> > <communityengine%2Bunsubscribe@ googlegroups.com>
> > > > .
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/communityengine?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "CommunityEngine" group.
> > To post to this group, send email to [email protected].
> > To unsubscribe from this group, send email to
> > [email protected]<communityengine%2Bunsubscribe@ 
> > googlegroups.com>
> > .
> > For more options, visit this group at
> >http://groups.google.com/group/communityengine?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"CommunityEngine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/communityengine?hl=en.

Reply via email to