Using drupal.org/project/moduleswith the Last Release filter and a Core Version filter causes incorrect results to appear. The listing should first be sorted by core version and then by release date rather than the other way around. For example at the time this was posted the module Gamertags was at the top of the list filtered by last release and for 5.x core; there was a 6.x release of Gamertags today, but the last 5.x release was September 29, 2007.
This is related to, but not a duplicate of these issues:
"Last release" same as "Last updated"?
Module browsing by version confusing when snapshot is not displayed
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 378830-3.project_solr_sort_facet.patch | 5.7 KB | pwolanin |
| #2 | 378830-2.project_solr_sort_facet.patch | 4.19 KB | dww |
| #1 | 378830-1.project_solr_sort_facet.patch | 3.44 KB | dww |
Comments
Comment #1
dwwYes, this was something we wanted to get working in the initial implementation of the project + solr integration, but we ran out of time at the Boston upgrade sprint, and haven't had time since to add the code to make this happen. However, pwolanin and I are working on this now at the DCDC code sprint, so we should hopefully have this done later today.
Here's an initial patch that handles one of the cases (if a core facet is enabled, the available sorts become specific to that version of core), and changes what fields we use when indexing project nodes so that we have real date fields (e.g. to support date range facets in the future) and so that everything is properly sortable. Still TODO: if a sort is active, and you select a core version facet, it should change which sort is active to use the version-specific one.
Comment #2
dwwStill broken, but closer.
Comment #3
pwolanin commentedComment #4
dwwComment #5
dwwEven though that was a cross-post, the patch did need work. ;) But, got it all working and committed to HEAD: http://drupal.org/cvs?commit=180360. Also committed a patch to bluebeach for the places we were looking in the solr document when theming project browse results.
Comment #6
dwwActually, I shouldn't really mark this fixed until we deploy on d.o -- hopefully later tonight.
Comment #7
dwwNow deployed and working fine on d.o. However, see #377736: Module filter or sort by release should impact what information is displayed for some related followup work we need to do now.