Pessoal, é necessário dar permissão extra em alguma pasta de instalação do openredu, para que se permita alterar/inserir imagem de profiles (de disciplinas)?
Tentei alterar o profile e exibiu o seguinte erro:
E no log:
Started GET “/images/environments/avatars/1/thumb_140/logo_forti.jpg?1471350930” for 10.1.2.104 at 2016-08-16 12:35:31 +0000
Served asset /ckeditor/ckeditor.js - 304 Not Modified (0ms)
Served asset /application.js - 304 Not Modified (6ms)
ActionController::RoutingError (No route matches [GET] “/images/environments/avatars/1/thumb_140/logo_forti.jpg”):
actionpack (3.2.13) lib/action_dispatch/middleware/debug_exceptions.rb:21:in call' actionpack (3.2.13) lib/action_dispatch/middleware/show_exceptions.rb:56:in
call’
railties (3.2.13) lib/rails/rack/logger.rb:32:in call_app' railties (3.2.13) lib/rails/rack/logger.rb:16:in
block in call’
activesupport (3.2.13) lib/active_support/tagged_logging.rb:22:in tagged' railties (3.2.13) lib/rails/rack/logger.rb:16:in
call’
actionpack (3.2.13) lib/action_dispatch/middleware/request_id.rb:22:in call' rack (1.4.5) lib/rack/methodoverride.rb:21:in
call’
rack (1.4.5) lib/rack/runtime.rb:17:in call' activesupport (3.2.13) lib/active_support/cache/strategy/local_cache.rb:72:in
call’
rack (1.4.5) lib/rack/lock.rb:15:in call' actionpack (3.2.13) lib/action_dispatch/middleware/static.rb:63:in
call’
railties (3.2.13) lib/rails/engine.rb:479:in call' railties (3.2.13) lib/rails/application.rb:223:in
call’
railties (3.2.13) lib/rails/railtie/configurable.rb:30:in method_missing' /usr/lib/ruby/vendor_ruby/phusion_passenger/rack/thread_handler_extension.rb:97:in
process_request’
/usr/lib/ruby/vendor_ruby/phusion_passenger/request_handler/thread_handler.rb:152:in accept_and_process_next_request' /usr/lib/ruby/vendor_ruby/phusion_passenger/request_handler/thread_handler.rb:113:in
main_loop’
/usr/lib/ruby/vendor_ruby/phusion_passenger/request_handler.rb:416:in block (3 levels) in start_threads' /usr/lib/ruby/vendor_ruby/phusion_passenger/utils.rb:113:in
block in create_thread_and_abort_on_exception’