Defect #6987
closedMissing template wiki/update.erb
0%
Description
Hi today we ran into Internal Error when trying to update previously deleted page.
The way to reproduce this is- Add wiki page
- Edit something on it
- Delete the page
- Add the page again
After that redmine throws this error:
Processing WikiController#update (for 10.0.1.207 at 2010-11-26 12:00:44) [PUT] Parameters: {"commit"=>"Save", "project_id"=>"alvila-admin", "action"=>"update", "_method"=>"put", "id"=>"TEST", "content"=>{"comments"=>"", "text"=>"h1. TEST\r\n\r\nNew page", "version"=>"0"}, "controller"=>"wiki", "attachments"=>{"=>{"description"=>""}}} ActionView::MissingTemplate (Missing template wiki/update.erb in view path vendor/plugins/menu_link/app/views:vendor/plugins/redmine-mylyn-connector/app/views:vendor/plugins/redmine_alvila_addons/app/views:vendor/plugins/redmine_charts/app/views:vendor/plugins/redmine_code_review/app/views:vendor/plugins/redmine_graphs_plugin/app/views:vendor/plugins/redmine_hudson/app/views:vendor/plugins/redmine_newissuealerts/app/views:vendor/plugins/redmine_time_tracker/app/views:vendor/plugins/timesheet_plugin/app/views:app/views): /usr/lib/ruby/1.8/webrick/httpserver.rb:104:in `service' /usr/lib/ruby/1.8/webrick/httpserver.rb:65:in `run' /usr/lib/ruby/1.8/webrick/server.rb:173:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start' /usr/lib/ruby/1.8/webrick/server.rb:162:in `start_thread' /usr/lib/ruby/1.8/webrick/server.rb:95:in `start' /usr/lib/ruby/1.8/webrick/server.rb:92:in `each' /usr/lib/ruby/1.8/webrick/server.rb:92:in `start' /usr/lib/ruby/1.8/webrick/server.rb:23:in `start' /usr/lib/ruby/1.8/webrick/server.rb:82:in `start' Rendering /opt/redmine-alvila/public/500.html (500 Internal Server Error)
ruby script/about
About your application's environment Ruby version 1.8.7 (x86_64-linux) RubyGems version 1.3.5 Rack version 1.0 Rails version 2.3.5 Active Record version 2.3.5 Active Resource version 2.3.5 Action Mailer version 2.3.5 Active Support version 2.3.5 Application root /opt/redmine-alvila Environment production Database adapter postgresql Database schema version 20101114115359 About your Redmine plugins Redmine Newissuealerts plugin 0.0.2 Issue Due Date 0.1.0 Mylyn Connector plugin 2.7.0.stable.RC3 Redmine Time Tracker plugin 0.3 Redmine Graphs plugin 0.1.0 Timesheet Plugin 0.6.0 Redmine Code Review plugin 0.4.0 Redmine Alvila Addons plugin 0.0.1 Menu Link Plugin 0.0.1 Redmine Hudson plugin 1.0.6 Redmine Charts 0.1.0
Files
Updated by Milan Stastny almost 14 years ago
The problem is somewhere else, the way to reproduce is wrong
There have been two separate links to the page one
[[Test]]
The other one
[[TEST]]
After that the internal error occurred. Seems like the page search is case insensitive but the page Update is case sensitive.
Updated by Jean-Philippe Lang almost 14 years ago
- Status changed from New to Closed
- Affected version (unused) changed from 1.0.3 to devel
- Resolution set to Fixed
- Affected version deleted (
1.0.3)
Updated by HyunKil Song over 13 years ago
- Status changed from Closed to Reopened
- Assignee set to Jean-Philippe Lang
Another way to reproduce like this
- A open wiki page 1 and edit something
- B open wiki page 1 and edit something
- A submit wiki page 1
- B submit wiki page 1
The Missing template wiki/update.erb error occurs.
Updated by HyunKil Song over 13 years ago
Concurrent editting in Wiki is very basic feature.
I tested in my env (1.1.1) and demo.redmine.org.
Updated by Alex Shulgin over 13 years ago
- File redmine-1.1-fix-missing-template-wiki-update-erb.patch redmine-1.1-fix-missing-template-wiki-update-erb.patch added
I was hit by this problem too (trying to update a wiki page which was updated in the way.)
Attached is an easy fix for this problem: render edit
template when leaving update
method from the rescue
block.
--
Alex
Updated by Jean-Baptiste Barth about 13 years ago
- Status changed from Reopened to Closed
I cannot reproduce on current trunk with HyunKil's steps, is it specific to postgresql ? Anyway, it's not the same problem as the original one, so I re-close this issue and encourage you to open a new one with detailed steps to reproduce the problem. Alex: thanks for your hint but I'd like to be sure to see which case it covers (with a test) before applying it.