BUG: Database Table name conflict with plugin redmine_contacts about redmine_tags HOT 4 CLOSED

Thank you for your report.

The problem lies in the way redmine_contacts implement taggings - they use their own implementation while redmine_tags uses acts_as_taggable_on. I'll contact developers of redmine_contacts in order to fix this problem ASAP.

from redmine_tags.

Thank you once again. I have discussed with Kirill (author of redmine_contacts) the problem and he upgraded his plugin to use same ruby gem as redmine_tags. Unfortunately there's still one problem left because of migrations which we are going to solve very soon. Right now you can install redmine_tags, and then redmine_contacts in order to avoid any problems and they will work both as a charm.

from redmine_tags.

Hmm i can't change the intsall order, because i already have redmine_contacts installed.
Whejn i migrate i get the error

Migrating redmine_tags...
== ActsAsTaggableOnMigration: migrating ======================================
-- create_table(:tags)
-> 0.0583s
-- create_table(:taggings)
rake aborted!
An error has occurred, all later migrations canceled:

Mysql::Error: Table 'taggings' already exists: CREATE TABLE taggings (id int(11) DEFAULT NULL auto_increment PRIMARY KEY, tag_id int(11), taggable_id int(11), tagger_id int(11), tagger_type varchar(255), taggable_type varchar(255), context varchar(255), created_at datetime) ENGINE=InnoDB

(See full trace by running task with --trace)

from redmine_tags.

Yes, I know, I had no time to write a new instructions. You need to remove migration from redmine_tags (it will be removed in the next release). To do so, simple remove following directory: redmine_tags/db/

from redmine_tags.