[VUFIND-627] Hard-coded publishDate in Advanced Search code Created: 12/Jul/12 Updated: 28/Feb/14 Resolved: 28/Feb/14 |
|
Status: | Resolved |
Project: | VuFind® |
Components: | Search |
Affects versions: | 1.3 |
Fix versions: | 2.3 |
Type: | Bug | Priority: | Minor |
Reporter: | Demian Katz | Assignee: | Demian Katz |
Resolution: | Fixed | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original estimate: | Not Specified |
Issue links: |
|
Description |
The Advanced Search code in web/services/Search/Advanced is hard-coded to look for the publishDate facet value for special date handling. This can cause problems if users choose a different field for use as a date range. We should investigate whether this can be made more generic, perhaps using the SpecialFacets/dateRange setting from facets.ini.
|
Comments |
Comment by Chelsea Lobdell [ 12/Jul/12 ] |
The hard coded references are actually in /interface/themes/blueprint/Search/advanced.tpl - Chelsea |
Comment by Demian Katz [ 12/Jul/12 ] |
We'll probably need to make some changes to both places -- the hard-coded field name in the module code is used for restoring settings when editing an existing advanced search. |