Opened 16 years ago
Closed 14 years ago
#266 closed defect (fixed)
GS2 and GS3: Casefolding is off by default even though prefs say it's on
| Reported by: | ak19 | Owned by: | nobody |
|---|---|---|---|
| Priority: | moderate | Milestone: | Greenstone 3 wishlist |
| Component: | Greenstone2&3 | Severity: | blocker |
| Keywords: | casefolding, preferences | Cc: |
Description
Tested on: GS3 compiled from source (checked out from svn on March 03, 2008) and on GS 2.80 binary installation.
When a collection is created in GLI with case-folding options available (Design tab > Search indexes > Casefold ticked), the Greenstone browser's preferences page says that the case-folding is ON (meaning searches performed should be case insensitive by default). However, casefolding starts being OFF by default in spite of what the preferences page says, so that searches made are case sensitive. Casefolding does not take effect until the Set-Prefs button is pressed (with casefolding status showing ON) which then turns the functionality ON.
See https://list.scms.waikato.ac.nz/mailman/private/greenstone-users/2008-March/006504.html for this problem identified by Jack Kelly.
Change History (4)
comment:1 by , 16 years ago
| Component: | Building → Greenstone2&3 |
|---|
comment:2 by , 15 years ago
| Milestone: | Next Release (2 or 3) → Release 2.82 |
|---|---|
| Severity: | → blocker |
comment:3 by , 15 years ago
| Milestone: | Release 2.82 → Release 3.04 |
|---|
comment:4 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
I have made the code defaults the same as interface defaults.
I think this may be a problem with other options too.
GS3: Quick solution, make the code defaults the same as the interface defaults.
Long term solution: I can't remember what that was, but I know I had an idea about it :-(