Currently, if the scripting engine for a filter is not available, it triggers an error message when executing the filter (for instance, the filter dialog currently asks for a ruby interpreter before it shows), while they should be disabled.
*** Bug has been marked as fixed ***.