评论：Redmine_Importer: Redmine CSV Import Plugin

来自：Gilles Ballanger

Gilles Ballanger — Mon, 17 May 2010 16:02:15 +0000

Hello,

I made a small modification to match viewer (for lazy user) it try to match the column name with the field name and if equal select the appropriate field.

here is the patch hope it can help :
—————–
### Eclipse Workspace Patch 1.0
#P redminePluginTicketImport
Index: src/issues_importer/app/views/importer/match.html.erb
===================================================================
— src/issues_importer/app/views/importer/match.html.erb
+++ src/issues_importer/app/views/importer/match.html.erb
@@ -14,8 +14,14 @@

+
:
- <%= select_tag "fields_map[#{column}]", "#{l(:option_ignore)}” + options_for_select( @attrs ) %>
+
+ <%= select_tag "fields_map[#{column}]", "#{l(:option_ignore)}” + options_for_select( @attrs , matchedsel) %>

来自：Greg Mefford

Greg Mefford — Wed, 10 Mar 2010 15:46:53 +0000

After doing some research, we solved the problem of getting this plugin to work on Redmine 0.9.x by using this fork of the plugin, which uses the new i18n API: http://github.com/rchady/redmine_importer/tree/

来自：Greg Mefford

Greg Mefford — Tue, 09 Mar 2010 19:44:02 +0000

We were looking to install this plugin for evaluation on our internal Redmine server and ran into a translation issue that seems like it wouldn’t be too complicated to fix, but I haven’t looked in to how to implement the fix yet.

we’re running Redmine 0.9.2 on Rails 2.3.4.
The error we are getting is similar to the ones listed above , for example:
“translation missing: en, label_issue_importer”

Is there a fix for this, or is there one in-progress?

Thanks!

来自：Pr016

Pr016 — Tue, 23 Feb 2010 09:42:12 +0000

Hi Martin, i was looking for the import of .csv into redmine and i found your plugin but when i tried it i had this problem (after the click on the button_upload)…
———————————————————————————–
vendor/rails/activesupport/lib/active_support/dependencies.rb:493:in `const_missing’
vendor/plugins/redmine_importer/app/controllers/importer_controller.rb:49:in `match’
vendor/rails/actionpack/lib/action_controller/base.rb:1166:in `send’
vendor/rails/actionpack/lib/action_controller/base.rb:1166:in `perform_action_without_filters’
vendor/rails/actionpack/lib/action_controller/filters.rb:579:in `call_filters’
vendor/rails/actionpack/lib/action_controller/filters.rb:572:in `perform_action_without_benchmark’
vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/1.8/benchmark.rb:293:in `measure’
vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue’
vendor/rails/actionpack/lib/action_controller/rescue.rb:201:in `perform_action_without_caching’
vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:13:in `perform_action’
vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in `cache’
vendor/rails/activerecord/lib/active_record/query_cache.rb:8:in `cache’
vendor/rails/actionpack/lib/action_controller/caching/sql_cache.rb:12:in `perform_action’
vendor/rails/actionpack/lib/action_controller/base.rb:529:in `send’
vendor/rails/actionpack/lib/action_controller/base.rb:529:in `process_without_filters’
vendor/rails/actionpack/lib/action_controller/filters.rb:568:in `process_without_session_management_support’
vendor/rails/actionpack/lib/action_controller/session_management.rb:130:in `process’
vendor/rails/actionpack/lib/action_controller/base.rb:389:in `process’
vendor/rails/actionpack/lib/action_controller/dispatcher.rb:149:in `handle_request’
vendor/rails/actionpack/lib/action_controller/dispatcher.rb:107:in `dispatch’
vendor/rails/actionpack/lib/action_controller/dispatcher.rb:104:in `synchronize’
vendor/rails/actionpack/lib/action_controller/dispatcher.rb:104:in `dispatch’
vendor/rails/actionpack/lib/action_controller/dispatcher.rb:120:in `dispatch_cgi’
vendor/rails/actionpack/lib/action_controller/dispatcher.rb:35:in `dispatch’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/rails.rb:76:in `process’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/rails.rb:74:in `synchronize’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/rails.rb:74:in `process’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:159:in `process_client’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in `each’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:158:in `process_client’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in `run’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in `initialize’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in `new’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:285:in `run’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in `initialize’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in `new’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel.rb:268:in `run’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:282:in `run’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in `each’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/configurator.rb:281:in `run’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:128:in `run’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/lib/mongrel/command.rb:212:in `run’
C:/Program Files/BitNami Redmine Stack/ruby/lib/ruby/gems/1.8/gems/mongrel-1.1.5-x86-mswin32-60/bin/mongrel_rails:281
C:/Program Files/BitNami Redmine Stack/ruby/bin/mongrel_rails:19:in `load’
C:/Program Files/BitNami Redmine Stack/ruby/bin/mongrel_rails:19
———————————————————————————

The session dump is this :

:importer_tmpfile: redmine_importer20100223-1764-ybk4vg-0
:importer_splitter: “,”
:importer_wrapper: “\”"
:user_id: 1
:importer_encoding: U
flash: !map:ActionController::Flash::FlashHash {}

Can you help me ?
Thanks, bye.

来自：Jack

Jack — Thu, 04 Feb 2010 06:41:57 +0000

“restart your redmine, do some config in permission settings”

Wow, thanks for the clear directions. Let me google “some config” and see what I can find.

来自：Luca Romanello

Luca Romanello — Wed, 03 Feb 2010 08:25:47 +0000

Hi Martin!
It’s me again…
I found a problem in your plugin when using it inside a mongrel_cluster with apache2 as a proxy balancer. As I tried to understand, when importing a csv in such an environment, there is a chance that between the first step of the import (that is, uploading the file) and the second one (submitting the mappings between header fields and issue attributes), the balancer decides to swap your request to another node of the cluster. When this happens, the plugin loses its handle on the file previously saved – of course, when there is just a node involved in the cluster (besides not being a true cluster… ), all works as expected.
I think this is related to the fact you are using a global variable Hash to store the handle to the file: my guess is that when the balancer swap to another node of the cluster, that variable in that node may not be initialized and, even if it is, doesn’t know anything about the file you uploaded on the other node.
I don’t know if this is a configuration issue of the proxy balancer or not, but I came to a patch on import_controller.rb:
I stored in session File.dirname(tmpfile.path), too, and then get it from session inside method result; then, instead of making
tmpfile = $tmpfiles[tmpfilename]
(which is the line that raises error)
I put
tmpfile = File.open(tmpfiledirname + “/” + tmpfilename)
where, of course, tmpfiledirname is the value I stored in session.
Now, like my previous comment, I don’t expect this to be a perfect patch, but until now it works. Hope this helps…

来自：zhaohl

zhaohl — Fri, 29 Jan 2010 01:25:40 +0000

missing lang when work with redmine-0.9-stable (svn: 3334)

translation missing: zh, label_importer
translation missing: zh, label_issue_importer
…..

redmine-importer version:
http://www.martinliu.info/wp-content/uploads/2009/04/redmine_importer-031.zip

来自：Christian Noack

Christian Noack — Fri, 15 Jan 2010 13:22:56 +0000

This plugin is really good, but using it did not work for me immediately. I encountered FasterCSV parsing errors and I miss a german localization. I’m running Redmine 0.8.7.stable on Mac OS X with Apache and Phusion/Passenger and Enterprise Ruby 1.8.7.
Therefore I did the fixes (binmode) mentioned above and added German localization. You can find the resulting plugin here:
http://github.com/chnoack/Redmine-Importer-Fixes

来自：iza

iza — Wed, 13 Jan 2010 07:09:25 +0000

hi martin,

i’m stuck with below error, pls help

ActionView::TemplateError (undefined method `-’ for nil:NilClass) on line #6 of importer/result.html.erb:
3:
4:
5:
6:
7:
8:
9: :

来自：Hubert Bakker

Hubert Bakker — Thu, 08 Oct 2009 08:56:40 +0000

Thanks for your plugin. I used it to import the issues from one Redmine implementation to another.
I finally got everything over.
Here are a couple of tips to ensure that the ID’s match between the two repositories.
Assumptions:
- the target database is a mysql database.
- there are no other projects in the target Redmine implementation

1. When you export the issues, make sure that the issues are in ascending order.
2. Massage the export file to fill the gaps of deleted issues
3. Set up the target implementation exactly like the source implementation.
4. Delete any issues in the target database using the ‘delete from issues’ command.
5. Ensure that the issues auto-increment numbering is reset using the ‘alter table issues auto_increment = 1′ command