- Issue created by @effortDee
- 🇺🇸United States tr Cascadia
I don't know if this field has ever been sortable in Views, or what has to be done to make it sortable. If someone wants to do that research please post here summarizing your findings and hopefully contribute a patch and a test case. New code like this should go into the current version 3.0.x, then they will be backported if possible after completion.
- 🇬🇧United Kingdom effortDee
TR it specifically says this in the description for the module "Easy-to-use integration with Views module for lists sorted by rating, or filtered by min/max ratings"
I just can't seem to make sense of the sort that it outputs and its been like this since we installed the module.
- 🇺🇸United States tr Cascadia
A lot of that description was written for the D7 (and pre-D7) version of the module. Some stuff never got ported to D8+, and I don't know if this is one of those things. I am working trying to clean up the mess and add tests and get the module back into prime working order, but I need help from the community too. I didn't write this code, I'm just trying to maintain and improve it and keep it working with all the changes made in core.
- 🇺🇸United States tr Cascadia
Basically, what I need is all information that is needed for me to reproduce the problem on a clean site. If I can't reproduce the problem on my own site then I can't fix it.
What I would need is a description of the steps you took to create the View, in the form of an export of a simple View that demonstrates the problem and that doesn't depend on any of your site-specific modules or content types etc. I would need an export of your Fivestar field configurations too so I can see how you configured the Fivestar field.
It would help if that same View worked with a core field, but failed with a Fivestar field. With this I could see what the core field is doing that makes it work, and have the fivestar field do the same thing. And I could use your View as a way to make sure that my changes fixed the problem and to turn into a real automated test that ensures this functionality doesn't get broken in the future.
I just don't have a lot of time right now to play around with views trying to do a simplified re-creation of the problem and to find a core field where the same view works. But once I have those things I don't think it will be too hard to fix Fivestar.