Image Filter Plugin: Error 500 when uploading asset to theme component

Just tried to upload an image asset to a newly created theme component and I get an error 500.

We’re on the latest version of Discourse, standard Install on a DO droplet. Image uploads in posts work.

Logs provide this error:

Failed to process hijacked response correctly : unexpected return

Summary

/var/www/discourse/plugins/discourse-image-filter/plugin.rb:66:in `block (2 levels) in activate!’

/var/www/discourse/lib/plugin/instance.rb:404:in `block in on’

/var/www/discourse/lib/discourse_event.rb:14:in `block in trigger’

/usr/local/lib/ruby/2.6.0/set.rb:338:in `each_key’

/usr/local/lib/ruby/2.6.0/set.rb:338:in `each’

/var/www/discourse/lib/discourse_event.rb:13:in `trigger’

/var/www/discourse/lib/upload_creator.rb:134:in `block in create_for’

/var/www/discourse/lib/distributed_mutex.rb:33:in `block in synchronize’

/var/www/discourse/lib/distributed_mutex.rb:29:in `synchronize’

/var/www/discourse/lib/distributed_mutex.rb:29:in `synchronize’

/var/www/discourse/lib/distributed_mutex.rb:14:in `synchronize’

/var/www/discourse/lib/upload_creator.rb:45:in `create_for’

/var/www/discourse/app/controllers/admin/themes_controller.rb:25:in `block (2 levels) in upload_asset’

/var/www/discourse/app/controllers/admin/themes_controller.rb:23:in `open’

/var/www/discourse/app/controllers/admin/themes_controller.rb:23:in `block in upload_asset’

/var/www/discourse/lib/hijack.rb:56:in `instance_eval’

/var/www/discourse/lib/hijack.rb:56:in `block in hijack’

/var/www/discourse/lib/scheduler/defer.rb:94:in `block in do_work’

rails_multisite-2.5.0/lib/rails_multisite/connection_management.rb:76:in `with_connection’

/var/www/discourse/lib/scheduler/defer.rb:89:in `do_work’

/var/www/discourse/lib/scheduler/defer.rb:79:in `block (2 levels) in start_thread’

Anybody?

1 Like

Found the problem. It’s caused by the image-filter-plugin.

@fzngagan you may want to look into this. The plugin causes errors when uploading assets to components when enabled.

2 Likes

This commit should fix the issue.

2 Likes