similar to: How do you test a module that extends ActiveSupport::Concern?

Hi, I''m facing a strange behavior in Rails with the has_many association and the generated collection<<(object, ...) method that comes along. I''ve got an Object model and a Tag model, plus a taggings table to join the two together. On Object, I set these associations: has_many :taggings, :as => :taggable, :dependent => :destroy has_many :tags,

class User<ActiveRecord::Base has_many :taggings, :as=>:taggable,:dependent=>true has_many :tags,:through=>:taggings end class Article<ActiveRecord::Base has_many :taggings, :as=>:taggable,:dependent=>true has_many :tags,:through=>:taggings end class Tagging<ActiveRecord::Base belongs_to :tag belongs_to :taggable,:polymorphic=>true end class Tag<ActiveRecord::Base

First of all, I should have gone to bed a long time, so please be forgiving with regards to what will follow :) So I''ve been working all day on a rails project that needs to go out soon, and I thought I would try to refactor a has_many relationship to a has_and_belongs_to_many relationship (using has_many :through). However, I then realized that I would loose a lot of the simple beauty

Didn''t have quite enough space to describe it there...basically i''m having a problem with the :uniq option in my tags. I''m using acts_as_taggable_on_steroid which adds these associations to my Resource class: Resource has_many :taggings, :as => :taggable, :dependent => :destroy, :include => :tag has_many :tags, :through => :taggings, :uniq => true

Josh Susser tells in his blog that the opposite direction of polymorphic will get into trouble together with has_many through. This is the url: http://blog.hasmanythrough.com/articles/2006/04/03/polymorphic-through I do that according to Josh Susser''s procedure: class Tagging < ActiveRecord::Base belongs_to :tag belongs_to :taggable, :polymorphic => true belongs_to

I''ve monkey patched this behavior into a gem and I was wondering if core would be interested in a PR to add Module#prepend support to ActiveSupport#Concern. I''ll add tests of course. The code is here: https://github.com/dockyard/easy_auth/blob/master/lib/easy_auth/active_support/concern.rb My monkey patch work for what I''m trying to do but I suspect a better

I have some models which share the same functionality just on other paths. So I decided to put these methods in a module and set the path in the model. My problem is that I''m not able to access the attribute in my module. my model: class Job < ActiveRecord::Base include ImageModel image_dir = "jobs"end my module: module ImageModel extend ActiveSupport::Concern

I have: module MySpike extend ActiveSupport::Concern included do class_attribute :foobar, instance_writer: true end end But, I want to be able to override the class attribute writer and/or instance writer method to do something when the attribute is set via self.foobar = true before or after calling super to set the attribute. Unfortunately, I can''t find a clean way

hey folks I''ve installed the plugin acts_as_taggable_on_steroids (henceforth aatos), and i already have some tagging functionality set up, using the same approach (ie a Tag and a Tagging class with associated tables) as aatos. So, i want my existing Tag and Taggings methods, plus some other methods i have in a module which i include with the taggable classes (ie the ones that would call

I''m trying to figure out the best way to set this data model up. I''m still pretty new to Rails, but hopefully I could turn this into something useful to others as well. Here are the basics: User has_many items items are taggable (items habtm taggings, tags habtm taggings) I also want users to be able to order their tagged items. So if I''ve tagged 5 items as

Hi! I''m observing some problems using gem inside Rails. My understanding is that after following sequence in irb: $ irb irb(main):001:0> require ''rubygems'' => true irb(main):002:0> require ''active_record'' => true irb(main):003:0> gem ''acts_as_taggable'' => true I should have access to acts_as_tagable mixins, like:

Working on Rails Engine. I want to make the controllers customizable whereever the Rails Engine is used. Therefore, I was trying to use `extend ActiveSupport::Concern` on the Engine controller class and include it in MyRailsApp. https://gist.github.com/4185823 # code in my rails engine moduel MyEngine class SomeController extend ActiveSupport::Concern def engine_some_method

hi, I started today to use the acts as taggable plugin and it''s working as expected. I added a method find_tagged_with_all since I needed to find the elements tagged with all the items in a list while find_tagged_with finds all the elements tagged with any of the list terms. Attached to this mail there''s a patch which adds the find_tagged_with_all method and which solves a

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?

Hi guys, I have encountered a strange error in one of my applications. The details are the following: The application is a very simple one, I have one model, Cards, it has some pretty basic stuff, some after_save methods for saving uploaded files to their places. I have an UI where I can manage the Card records, with the default methods, including ''edit'' cards_controller.rb:

Hi all, I''m trying to extend the tagging functionality of has_many_polymorphs to work with user owned tags - ie, putting belongs_to :user in the Tagging model. So I changed the index in the generated migration, and added user_id to the taggings table. Then I added belongs_to :user in the Tagging model. In the lib/tagging_extensions.rb file I added a new function: def

Like most people, I''ve got two machines: one for development and one for production. I''ve done everything I can to make sure the ruby/rails environments are the same, but of course they''re not identical (I''ll get into that in a moment). The error that I''m getting happens when I call a method in a background task controller on the production machine; I

I have this code that is using svn externals with rails EDGE working fine for the past couple of months. A couple of days ago, this code died. Even after deleting vendor/rails, this code doesnt work: class Tag < ActiveRecord::Base has_many :taggings has_many :events, :through => :taggings has_many :users, :through => :taggings end class User < ActiveRecord::Base # Virtual

I''m writing a Rails plugin from scratch and recently generating models inside it. In fact, i''m trying to follow the guide from http://guides.rubyonrails.org/plugins.html so i used the following code taken from this site in order to make the models appear like files in the main app directory (as it was said) this is the code: %w{ models }.each do |dir| path =

Upgrading a Rails app from 2.2 to 2.3.2 (via 2.3.0). Got things working in the browser, but script/console seems messed up in both 2.3.0 and 2.3.2: $ script/console Loading development environment (Rails 2.3.2) /Library/Ruby/Gems/1.8/gems/rails-2.3.2/lib/initializer.rb:56:in `env'':NameError: uninitialized constant Module::ActiveSupport