v1.4.9 (Production Release)

Release 1.4.9 is the ninth minor update to Release 1.4, which was the fifth major release of staticSearch. It has only the following changes:

• Documentation has been brought up to date with recent changes.

All issues and tickets related to version 1.4 can be found here and here.

v1.4.8 (Production Release)

Release 1.4.8 is the eighth minor update to Release 1.4, which was the fifth major release of staticSearch. It has only the following changes:

• We have fixed a bug which caused a VERSION file to be created containing a git error message if the user chose to customize the test suite instead of creating their own configuration. A random version identifier is created instead.

All issues and tickets related to version 1.4 can be found here and here.

v1.4.7 (Production Release)

Release 1.4.7 is the seventh minor update to Release 1.4, which was the fifth major release of staticSearch. It has only the following changes:

• A bug which caused a tokenization error because the XSLT processor was using an old Unicode dataset has been handled with a temporary workaround, adding the codepoint U+A78F to the tokenization mechanism.
• When searching for a phrase containing an ampersand, the phrase would be successfully found, but if the same search was reloaded from the browser URL, it would fail. This has now been corrected. Thanks to the TMP team for reporting this.

All issues and tickets related to version 1.4 can be found here and here.

v1.4.6 (Production Release)

Release 1.4.6 is the sixth minor update to Release 1.4, which was the fifth major release of staticSearch. It has only the following changes:

• A bug which caused weighting values to be lost during tokenizing has been corrected.
• The mechanism which scrolls the search page automatically to display search results has been adjusted in an attempt to avoid hiding the first result(s) behind a sticky or fixed page header.
• The build process has been modified in an attempt to ensure that the search page which is generated contains one and only one charset declaration.
• A warning is now issued when no title is found for a document being indexed. This situation means that any search results will be less useful to the end user because no document title can be displayed for the document.

All issues and tickets related to version 1.4 can be found here and here.

v1.4.5 (Production Release)

Release 1.4.5 is the fifth minor update to Release 1.4, which was the fourth major release of staticSearch. It has only two changes:

• Two configuration parameters, <stopwordsFile> and <dictionaryFile>,
  were previously documented as optional, but in fact the build process requires them. The
  documentation has been updated.
• There was a mismatch between files which were included in the indexing process and
  files which were checked for well-formedness ahead of indexing; it was possible for files
  that were not intended to be indexed at all to be checked and fail the well-formedness
  test even though they were not part of the build. This has been fixed.

All issues and tickets related to version 1.4 can be found here and here.

v1.4.4 (Production Release)

Release 1.4.4 is the fourth minor update to Release 1.4, which was the fourth major release of staticSearch. It has only one change:

• A deprecated JavaScript function, substr(), which was
  used in one line of code only, has been replaced by substring().

All issues and tickets related to version 1.4 can be found on GitHub.

v1.4.3 (Production Release)

Release 1.4.3 is the third minor update to Release 1.4, which was the fourth major release of staticSearch. It has only one change:

• A new method has been added to the StaticSearch class: preProcessSearchString(), which is called from parseSearchQuery(), does nothing as it is defined, but can be overridden by end-users to enable them to do any special processing they might need to do on an input search string. This is sometimes necessary when (for example) specific diacritics are being ignored by the search indexing, but end-users might type them in anyway. The search string is also being unicode-normalized (to NFC) at the beginning of the parsing function.

All issues and tickets related to version 1.4 can be found on GitHub.

v1.4.2 (Production Release)

Release 1.4.2 is a second minor update to Release 1.4, the fourth major release of staticSearch. It has only one change:

• A bug which could cause a divide-by-zero error in the JSON generation stage of the build when the target site consisted of fewer than ten documents was fixed via a pull request (#249) from Norman Walsh (@ndw). Thanks Norman!

All issues and tickets related to version 1.4 can be found on GitHub.

v1.4.1 (Production Release)

Release 1.4.1 is a minor update to Release 1.4.0, which is the fourth major release of staticSearch. It has only one change:

• A minor bug (issue #220) whereby a rare combination of circumstances could lead to document hit scores being reported as concatenated numbers rather than summed numbers has been fixed.

All issues and tickets related to version 1.4 can be found on GitHub.

v1.4.0 (Production Release)

Release 1.4.0 is the fourth major release of staticSearch. It includes the following (for more detailed information, see the documentation):

Deprecations requiring changes to existing projects:

• Filter sort keys must be declared using the all lower-cased data attribute data-ssfiltersortkey. While the documentation correctly specified the attribute's name, the processing code only accepted the camel-case version, which is invalid XHTML5. In 1.4, using @data-ssFilterSortKey will result in WARNINGs; in all subsequent versions, using the camel-case attribute name will result in build failures.

New features and enhancements:

• A new "Search Only In" feature has been added. This enables you to specify regions of documents and label them using the label attribute on <context> per issue #20). Users can then check only the regions they would like to get search results from.
• A new "feature filter" has been added to the collection of search facets. This provides an option for cases where the number of items in a description filter might be so large that providing a long list of individual checkboxes for all the options is not practical. Instead, the feature filter offers a method of finding and selecting items using a typeahead control.
• Search page controls are now WCAG2-compliant.
• When you navigate back or forward to a previous search, if any of the filters which were used in that search are hidden inside closed HTML details elements, those elements will be opened.
• A <noscript> element is now inserted into the search page to handle cases where JavaScript is turned off in the user's browser.
• A ‘Loading...’ splash screen is shown when the search page is initially configuring itself.
• All inline CSS and JavaScript has now been moved to external files, to better suit Content Security Policy constraints.
• The staticSearch report has been simplified and no longer produces a concordance of stems by default. The concordance can be built at the command line by calling the concordance target in ant
• The version attribute has been added to the root <config> element to better future-proof the alignment of configuration files and the staticSearch codebase.

Bug Fixes

• A bug which caused number filters to be ignored when navigating back to a previous search has been fixed.
• A bug which caused the tokenizer to assume wordbreaks when encountering certain diacritics has been fixed.

All issues and tickets related to version 1.4 can be found on GitHub.