1.0.0 - Context Menu on Issue Overview not working as before
Added by Lars Scheithauer over 14 years ago
In version 0.9.4 and before, a right-click on an issue brought up the context menu, where you could change various metainformation on issues. After a click, the requested change was done immediatly.
Now, in 1.0.0, the usual edit-page for an issue is shown before the changes can be made. Is there any way to get the old behaviour back?
Best Regards,
Lars
Replies (5)
RE: 1.0.0 - Context Menu on Issue Overview not working as before - Added by Felix Schäfer over 14 years ago
AFAIK this only broke on status changes and a fix for that has been committed on Sunday (I think).
[closed] RE: 1.0.0 - Context Menu on Issue Overview not working as before - Added by Lars Scheithauer over 14 years ago
RE: 1.0.0 - Context Menu on Issue Overview not working as before - Added by Fabio Leitao over 14 years ago
It was working for me on 1.0.1, but since last update to r4045 it has been causing error 500 on the log and nothing shows up... by the way, I believe one of those upgrades has removed the context_menu.rhtml file from the views, and I am not sure what it has been replaced by.
RE: 1.0.0 - Context Menu on Issue Overview not working as before - Added by Fabio Leitao over 14 years ago
Fabio Leitao wrote:
It was working for me on 1.0.1, but since last update to r4045 it has been causing error 500 on the log and nothing shows up... by the way, I believe one of those upgrades has removed the context_menu.rhtml file from the views, and I am not sure what it has been replaced by.
Sorry, the last upgrade was to r4051...
RE: 1.0.0 - Context Menu on Issue Overview not working as before - Added by Fabio Leitao over 14 years ago
I have been getting this error 500 (debug level) when I right click the issue (expecting a context menu):
Processing IssuesController#context_menu (for 1##.6#.2##.6# at 2010-09-05 23:28:39) [POST] Parameters: {"back_url"=>"/projects/ads/issues", "ids"=>["54"], "project_id"=>"ads", "action"=>"context_menu", "authenticity_token"=>"4LkGjEq8x8to/rL5b9U/VppzMcwi3xAcTF7bY5YPk0o=", "controller"=>"issues", "_"=>""} SQL (0.2ms) SELECT max(`settings`.updated_on) AS max_updated_on FROM `settings` User Load (0.2ms) SELECT * FROM `users` WHERE (`users`.`id` = 3) AND (users.status = 1) AND ( (`users`.`type` = 'User' OR `users`.`type` = 'AnonymousUser' ) ) ArgumentError (wrong number of arguments (0 for 1)): /usr/lib/ruby/1.8/mongrel.rb:159:in `process_client' /usr/lib/ruby/1.8/mongrel.rb:158:in `each' /usr/lib/ruby/1.8/mongrel.rb:158:in `process_client' /usr/lib/ruby/1.8/mongrel.rb:285:in `run' /usr/lib/ruby/1.8/mongrel.rb:285:in `initialize' /usr/lib/ruby/1.8/mongrel.rb:285:in `new' /usr/lib/ruby/1.8/mongrel.rb:285:in `run' /usr/lib/ruby/1.8/mongrel.rb:268:in `initialize' /usr/lib/ruby/1.8/mongrel.rb:268:in `new' /usr/lib/ruby/1.8/mongrel.rb:268:in `run' Rendering /home/corp/www/rails/redmine/public/500.html (500 Internal Server Error)
I am not sure if some plugin or upgrade crippled the function, and I am not sure where to look for ...