[#VUFIND-307] Translated facets cause invalid search results on advanced search screen. - VuFind Issue Management

Details

Type: Bug
Status: Resolved
Priority: Trivial
Resolution: Fixed
Affects Version/s: 1.0
Fix Version/s: 1.0.1
Component/s: Search
Labels:
None

Description

If you select a facet from one of the menus at the bottom of the Advanced Search screen and you are in a language other than English, the translated value of the filter rather than the raw value gets passed through to the search, causing zero results.

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

Demian Katz added a comment - 13/Aug/10 11:29 AM

Fixed in r2930.

Show

Demian Katz added a comment - 13/Aug/10 11:29 AM Fixed in r2930.

Hide

Permalink

Alexandros Tsiokos added a comment - 09/Nov/10 6:06 AM

I believe this issue still exists. In r3065 i still have the same problem. One can check it in the demo installation with "German" as language for example.

Show

Alexandros Tsiokos added a comment - 09/Nov/10 6:06 AM I believe this issue still exists. In r3065 i still have the same problem. One can check it in the demo installation with "German" as language for example.

Hide

Permalink

Demian Katz added a comment - 09/Nov/10 9:22 AM

The reason that the problem was reproducible in the demo at http://vufind.org/demo is that this version of VuFind had never been upgraded past version 1.0. As of this morning, I have updated the demo to use release 1.0.1, and the problem now seems to have gone away. I am now unable to reproduce the issue in the demo, and I am also unable to reproduce it using the current trunk. Have you confirmed that the diffs made in r2930 have been included in the copy of VuFind you are working with? If they are there, could you provide more details on how to reproduce the problem?

Show

Demian Katz added a comment - 09/Nov/10 9:22 AM The reason that the problem was reproducible in the demo at http://vufind.org/demo is that this version of VuFind had never been upgraded past version 1.0. As of this morning, I have updated the demo to use release 1.0.1, and the problem now seems to have gone away. I am now unable to reproduce the issue in the demo, and I am also unable to reproduce it using the current trunk. Have you confirmed that the diffs made in r2930 have been included in the copy of VuFind you are working with? If they are there, could you provide more details on how to reproduce the problem?

People

Assignee:

Unassigned

Reporter:

Demian Katz

Vote (0)

Watch (1)

Dates

Created:

13/Aug/10 11:29 AM

Updated:

09/Nov/10 9:22 AM

Resolved:

13/Aug/10 11:29 AM