Appliance update: texisScripts-21.1.0, applianceman-21.1.0, texis-7.06.15312...

Post Reply
User avatar
Kai
Site Admin
Posts: 1271
Joined: Tue Apr 25, 2000 1:27 pm

Appliance update: texisScripts-21.1.0, applianceman-21.1.0, texis-7.06.15312...

Post by Kai »

Three appliance updates are now available: texisScripts-21.1.0, applianceman-21.1.0, and texis-7.06.15312...

----------

texisScripts-21.1.0 has the following fixes and improvements; note the caveats denoting behavior changes etc., especially with Group By:

* Caveat: Group By bins now support explicit full ranges (e.g. 10..20) instead of just separators, and may overlap or have gaps; Bin Separators now renamed to Bin Ranges. Note that number of ranges and display names must now be equal, so an extra leading range must be added (or leading Display Name removed) from existing Bin Ranges / Bin Display Names.

* Caveat: Searches with proximity set to other than page (i.e. line, sentence, or paragraph) were not respecting the Allow Post-Processing setting: post-processing was silently enabled regardless. Fixed: Such searches now require Allow Post-Processing to be enabled (i.e. in case admin wishes to prevent slow/long-running queries by disabling).

* Caveat: Proximity widget on Advanced Search form now does not appear if Allow Post-Processing is not enabled (default), because non-page proximity searches require post-processing. XML output now includes a <Feature name="proximity" isEnabled="Y"> element if Proximity is enabled.

* Caveat: Added Prevent Find Similar Fetch setting to prevent custom Find Similar searches from fetching URLs not in the profile database; also fixed issues where database lookup was not done properly, and where failed fetches' text was still used
Add options for sorting URL query string variables and for lowercasing query string values.

* <UserResultsPerPage> element added to XML output to indicate user-submitted results per page

* Add autocomplete="off" to all password inputs.

* A Find Similar query might show an estimated document count without indicating it as such, e.g. when there is an additional Parametric query; fixed

* Renamed Modify Date to Modified in Data from Field To Field list, for consistency with other usage

* Find Similar now uses Index Fields as source text to generate its query, instead of hard-coded list

* A Find Similar search immediately after Search Settings are updated could fail with Reference URL id not found in profile database error; fixed

* Some UTF-8 Unicode punctuation characters in queries -- such as U+201C/U+201D double-quotes -- are now canonicalized to their ASCII equivalents, to support iOS Smart Punctuation and similar Unicode double-quoted searches

* Fixed help links for settings that require parametric fields to exist (Parametric Search Query, Group By, etc)

* Upgraded to JQuery 3.3.1 and JQueryUI 1.12.1
----------

applianceman-21.1.0 is a documentation update.

----------

texis-7.06.15312... provides the following fixes and improvements:

* w/N (within N words) queries -- when multiple Word Definition (index) expressions are set -- no longer require post-processing and thus run faster. This makes w/N queries a potential faster alternative for Proximity queries (line/sentence/paragraph) that require post-processing. In rare cases increasing the value of w/N may be needed to return some results containing an intervening word that matches expressions multiply.

* Redirects from invoking search or dowalk scripts without a trailing slash in the URL were not escaping the URL in the HTML of the redirect, allowing a potential XSS attack (JavaScript injection); fixed

* A multiple-term relevance-ordered query with a w/N operator might erroneously cause a post-processing message (... w/N delimiter used with multiple index expressions and (indexwithin & 0x8) is off); fixed

* PDF title etc. meta data may have had hi-bit/UTF-8 characters output wrong; fixed

* Try to work around some broken PDFs with incorrectly set Creator or other meta data as unescaped Windows paths

* An HTTPS URL fetched through a proxy (tunnel) may not have had SSL options (SSL Client Protocols, SSL Client Ciphers, SSL Use SNI) set; fixed

These updates are available via the System -> System Setup -> Update Software menu.
Post Reply