acts_as_taggable and acts_as_ordered_taggable clobber each other

[pjungwir]

Each time you use acts_as_taggable or acts_as_ordered_taggable in your class, core.rb redefines the methods for all the tag types, including ones already defined from a previous acts_as_taggable or acts_as_ordered_taggable line.

You can test this by adding a puts to core.rb:

def initialize_acts_as_taggable_on_core
    tag_types.map(&:to_s).each do |tags_type|
      puts "----------------------------------------#{tags_type} (#{preserve_tag_order?})----------------------"
      tag_type         = tags_type.to_s.singularize
      # . . .

Now suppose you define your model like so:

class Foo
  acts_as_taggable_on :skills
  acts_as_ordered_taggable_on :books, :music
  acts_as_taggable_on :interests
  # . . .

When Foo loads, you see this printed:

----------------------------------------skills (false)----------------------
----------------------------------------skills (false)----------------------
----------------------------------------books (true)----------------------
----------------------------------------music (true)----------------------
----------------------------------------skills (false)----------------------
----------------------------------------books (false)----------------------
----------------------------------------music (false)----------------------
----------------------------------------interests (false)----------------------

This means that you can't mix ordered and unordered tag types in the same class. Whatever kind of tag type you define last sets the ordered property for all previously-defined tag types.

[shekibobo]

This may be related to #339. Could you check your test again against this PR?

[tilsammans]

#339 was just merged into master, so you can use master branch for testing.