Bug #2353
Can not create Macro on Redmine 1.4.2
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
11 Dec 2014
Due date:
% Done:
0%
Redmine version:
External issue:
Description
No errors on install of 1.0.0b but when try to create even the simplest macro I get a 500 error.
Log says:
NoMethodError (private method `class_variable_get' called for Redmine::WikiFormatting::Macros:Module): vendor/plugins/wiking/app/models/wiki_macro.rb:114:in `validate_name' vendor/plugins/wiking/app/controllers/macros_controller.rb:18:in `create' passenger (4.0.29) lib/phusion_passenger/rack/thread_handler_extension.rb:77:in `process_request' passenger (4.0.29) lib/phusion_passenger/request_handler/thread_handler.rb:140:in `accept_and_process_next_request' passenger (4.0.29) lib/phusion_passenger/request_handler/thread_handler.rb:108:in `main_loop' passenger (4.0.29) lib/phusion_passenger/request_handler.rb:441:in `start_threads' passenger (4.0.29) lib/phusion_passenger/request_handler.rb:435:in `initialize' passenger (4.0.29) lib/phusion_passenger/request_handler.rb:435:in `new' passenger (4.0.29) lib/phusion_passenger/request_handler.rb:435:in `start_threads' passenger (4.0.29) lib/phusion_passenger/request_handler.rb:434:in `times' passenger (4.0.29) lib/phusion_passenger/request_handler.rb:434:in `start_threads' passenger (4.0.29) lib/phusion_passenger/request_handler.rb:433:in `synchronize' passenger (4.0.29) lib/phusion_passenger/request_handler.rb:433:in `start_threads' passenger (4.0.29) lib/phusion_passenger/request_handler.rb:200:in `main_loop' passenger (4.0.29) helper-scripts/classic-rails-preloader.rb:182
Any suggestions?
History
#1 Updated by Rob Spearman about 10 years ago
Server error on 2.5.3 as well.
#2 Updated by Rob Spearman about 10 years ago
Removing, pulling from SVN, and reinstalling fixed the issue with 2.5.3.
#3 Updated by Andriy Lesyuk over 8 years ago
- Status changed from New to Incomplete
Rob, does creating macros work?
#4 Updated by Andriy Lesyuk about 7 years ago
- Status changed from Incomplete to Closed
Assuming, that the issue has been fixed.