Open gc-olivierho opened 7 years ago
For those encountering the same issue, upgrading the above-mentioned gem to version 0.10.7 fixed the issue (changed in the Gemfile to 'active_model_serializers', '~> 0.10.7'). [edited - 2018/04/10] However, active_model_serializers 0.10 does not implement the root member anymore (see https://github.com/rails-api/active_model_serializers/issues/1683), so you'll have to remove the self.root = false in the serializer files. Moreover, I still haven't succeeded in using ElasticSearch 2.0 with Redmine 3.4.4 so far.
For whoever would like to get the Elasticsearch plugin to work with Redmine 3.4.x, or to debug the current code... I finally got it to work by reverting the active_model_serializer gem dependency back to version 0.7.0.
The issue with Redmine 3.4.x is that now Redmine retrieves filter data dynamically with ajax calls. In particular, the ajax call to
I tried many things in v0.8 to disable serializing for queriesController#filter, but failed with all my attempts. I tried to understand how to replace the self.root = false in the serializers when using v 0.10.0, but could not find what to do.
So finally, changing the gemfile to reference :
'active_model_serializers',
'~> 0.7.0'
was the only way I found to make the redmine_elasticsearch plugin work with Redmine 3.4.x.
After upgrading to Redmine 3.4.2 (from 3.3.3), I got the following behavior:
Go to a project, Issues tab
Filters -> Add Assignee Result: the list of assignees to filter on is empty.
Removing redmine_elasticsearch from the plugins fixes the issue
More precisely, removing (commenting) the reference to the gem
in the Gemfile fixes the issue. I'm sorry I can't go further in the analysis, the code of the elasticsearch plugin is far beyond my understanding capabilities :(