TemplateError when viewing issue details after upgrading 1.3.3 to 1.4.1
Added by Franz S over 12 years ago
Hello communtiy,
I upgraded Redmine from 1.3.3 to 1.4.1. I started with a new checkout and just copied the configuration files (database and configuration), one plugin (hudson) and the files folder.
Database migration went fine. The new installation runs but I have one serious problem. If I want to see the details of an issue which has comments I get the following error message:
Processing IssuesController#show (for ***.***.***.*** at 2012-05-07 18:44:17) [GET] Parameters: {"action"=>"show", "id"=>"15", "controller"=>"issues"} Rendering template within layouts/base Rendering issues/show ActionView::TemplateError (No route matches {:action=>"activity", :controller=>"projects", :from=>Thu, 26 Jan 2012, :id=>nil}) on line #85 of app/views/issues/show.html.erb: 82: <%= link_to_attachments @issue %> 83: <% end -%> 84: 85: <%= call_hook(:view_issues_show_description_bottom, :issue => @issue) %> 86: 87: <% if !@issue.leaf? || User.current.allowed_to?(:manage_subtasks, @project) %> 88: <hr /> lib/redmine/hook.rb:63:in `send' lib/redmine/hook.rb:63:in `call_hook' lib/redmine/hook.rb:63:in `each' lib/redmine/hook.rb:63:in `call_hook' lib/redmine/hook.rb:60:in `tap' lib/redmine/hook.rb:60:in `call_hook' lib/redmine/hook.rb:146:in `call_hook' app/views/issues/show.html.erb:85 app/controllers/issues_controller.rb:118:in `show' app/controllers/issues_controller.rb:115:in `show' /usr/lib/ruby/1.8/phusion_passenger/rack/request_handler.rb:92:in `process_request' /usr/lib/ruby/1.8/phusion_passenger/abstract_request_handler.rb:207:in `main_loop' /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:418:in `start_request_handler' /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:358:in `handle_spawn_application' /usr/lib/ruby/1.8/phusion_passenger/utils.rb:184:in `safe_fork' /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:354:in `handle_spawn_application' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in `__send__' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in `main_loop' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:196:in `start_synchronously' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:163:in `start' /usr/lib/ruby/1.8/phusion_passenger/railz/application_spawner.rb:213:in `start' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:262:in `spawn_rails_application' /usr/lib/ruby/1.8/phusion_passenger/abstract_server_collection.rb:126:in `lookup_or_add' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:256:in `spawn_rails_application' /usr/lib/ruby/1.8/phusion_passenger/abstract_server_collection.rb:80:in `synchronize' /usr/lib/ruby/1.8/phusion_passenger/abstract_server_collection.rb:79:in `synchronize' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:255:in `spawn_rails_application' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:154:in `spawn_application' /usr/lib/ruby/1.8/phusion_passenger/spawn_manager.rb:287:in `handle_spawn_application' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in `__send__' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:352:in `main_loop' /usr/lib/ruby/1.8/phusion_passenger/abstract_server.rb:196:in `start_synchronously' /usr/lib/phusion_passenger/passenger-spawn-server:61 Rendering /var/lib/redmine/public/500.html (500 Internal Server Error)
I tried to figure out the problem but I don't have any clue. There is just one thing I could think about. In the old version the 'Commit Relation Editor' plugin was installed. I did not install this in the new version because this has built in this feature. Could this be the problem? How could I solve it?
Thank you very much for your help!
Franz
Replies (2)
RE: TemplateError when viewing issue details after upgrading 1.3.3 to 1.4.1 - Added by Franz S over 12 years ago
It works when I deactivate the Hudson plugin. So it seems to be a problem with this plugin.
RE: TemplateError when viewing issue details after upgrading 1.3.3 to 1.4.1 - Added by Franz S over 12 years ago
Problem solved with the new version of the Hudson plugin 1.0.8.1
see topic Hudson Plugin 1.0.5