Redmine Tags

Allows marking up different models in Redmine with tags. Inspired by original redmine_tags of Eric Davis.

Supported models

• Issues

Requirements

• Redmine >= 1.2.0
• acts-as-taggable-on = 2.1.0

Installation

• Follow the Redmine plugin installation steps and make sure the plugin is installed to vendor/plugins/redmine_tags
• Install acts-as-taggable-on NOTICE: skip this step if you have redmine_contacts plugin installed
  • Run migration generator: script/generate acts_as_taggable_on_migration
  • Run migration: rake db:migrate
• Restart your Redmine web servers (e.g. mongrel, thin, mod_rails)

Migrating from 1.x to 2.x

As of 2.0.0 redmine_tags is not compatible with 1.x branch.

So the easiest way to install redmine_tags 2.x is to completely uninstall previously installed redmine_tags 1.x first and then installing new version. Alternatively you can "fix" migration names in the database, but that requires some skills and understanding of are you doing. If you are brave enough, follow the steps below.

NOTICE Please, read FAQ before doing anything of below.

WARNING I take no reponsibility for any possible data loss.

Since version 2.0.0 redmine_tags do not provides database migration for acts-as-taggable-on plugin. So in order to migrate properly you will need to make that migration as if it was installed to the main rails application.

First of all, move the migration script from plugin to main app:

$ cp ./vendor/plugins/redmine_tags/db/migrate/001_acts_as_taggable_on_migration.rb \
     ./db/migrate/20120101000000_acts_as_taggable_on_migration.rb

Make sure to change 001_ prefix to 20120101000000_. Now connect to your database and replace redmine_tags schema migration entry with just created one:

DELETE FROM `schema_migrations` WHERE `version` = '1-redmine_tags';
INSERT INTO `schema_migrations` (`version`) VALUES ('20120101000000');

That's all. :))

F.A.Q.

Why do I need to "fix" migration script name?

This will allow to safely migrate down when you will decide to uninstall plugin in future. Also this will allow to be sure that only one migration of acts-as-taggable-on exists (when it's used by other plugins as well).

Why can't you simply check if migration needed, like some other plugins?

I don't like "conditional" migrations. I don't think it's a good practice and will not go this way unless it will be the only possible solution.

I'm using redmine_contacts plugin. Do I need to fix db migration on upgrade?

If you are using redmine_contacts plugin, you may simply remove redmine_tags db migration script and it's record in schemas_migration registry. As both plugins use acts-as-taggable-on for tagging support, it's quiet safe to simply remove redmine_tags database migration with SQL query:

DELETE FROM `schema_migrations` WHERE `version` = '1-redmine_tags';

License

This plugin is licensed under the terms of GNU/GPL v3+. See COPYING and LICENSE for details.