| Summary: | defaultSortOrder and OPACdefaultSortOrder are set to "ascending" on install | ||
|---|---|---|---|
| Product: | Koha | Reporter: | D Ruth Holloway <ruth> |
| Component: | Searching | Assignee: | D Ruth Holloway <ruth> |
| Status: | CLOSED FIXED | QA Contact: | Jonathan Druart <jonathan.druart> |
| Severity: | trivial | ||
| Priority: | P5 - low | CC: | chris, jonathan.druart, nengard, paul.poulain |
| Version: | 3.8 | ||
| Hardware: | All | ||
| OS: | All | ||
| See Also: | http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6092 | ||
| Change sponsored?: | --- | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Attachments: |
Proposed patch
Bug 8012: default values for defaultSortField/defaultSortOrder NULL on install |
||
|
Description
D Ruth Holloway
2012-04-27 02:03:05 UTC
A little investigation showed that this value is actually initialized NULL--which you can't set in the interface--which shows "ascending." But the actual behavior of the sort is kinda screwy by that. To me, it makes sense to initialize the value to SOMETHING... Created attachment 11659 [details] [review] Proposed patch Created attachment 11675 [details] [review] Bug 8012: default values for defaultSortField/defaultSortOrder NULL on install ...which *looks* like "relevance/ascending" in the staff client, which doesn't make sense. This patch initializes the values at "relevance/descending", which is a functional combination. Signed-off-by: Chris Cormack <chris@bigballofwax.co.nz> QA Comment: Set the default sort order to relevance desc. Seems logical. Marked as Passed QA *** Bug 4221 has been marked as a duplicate of this bug. *** Patch pushed to master Pushed to 3.8.x, will be in 3.8.5 |