Build Compatibility

• 2.1.x is compatible with CMS 9 releases up to 9.5.
• 2.2.x through 2.8.x is compatible with CMS 9.6 - 9.8.
• 2.9.x - 2.14.x is compatible CMS 9.6+ and CMS 10.0 - 10.3

  Note: New Asset indexing enhancements in 2.13+ are only supported in CMS 10.3+. Refer to the notes on Legacy Asset Indexing if you are indexing content from CMS 10.2 and below.

InSite Search 2.13.44 - December 31, 2019

• Asset indexing is now optimized so that changes to metadata or categorization to assets do not require full asset re-indexing.

  Note: This optimization applies to CMS 10.3+ published content only. For customers publishing from CMS 10.2 or below, refer to the note in Legacy Asset Indexing Mode.

• Added optimizations to asset binary file indexing, along with additional logging output during binary file indexing.
• Renamed Assets from CMS 10 would previously not trigger a re-index of the assets. Now, when an asset is renamed, the indexer creates a new record for the newly-renamed asset. In order to remove the previous asset entry, a full publish will need to occur so that the indexer is aware of the binary file no longer being present on disk.
• Added two new attribute settings for QueryFields.xml entries: 1) partialfieldnamematch, which allows for partial field name support, and 2) wildcard. See QueryFields for details.
• Keymatch now supports a fifth data column, Abstracts, which can be used to provide abstract text to be returned with a keymatch search result.
• The sample SiteCrawlerSource.config file contained a misspelling in the useCanonicalUrlInHtml setting.
• Exact phrase search is now supported by encapsulating multiple terms in double quotes. This feature neither supports spell checking nor does it accept additional terms that do not match the exact phrase passed into the query.

  Note: This may cause performance issues if your query includes fields with large bodies of text (e.g., fulltext fields) and is not recommended for all implementations.

• Added the urlExclusionPrefixes configuration for HTML Site Crawler to exclude indexing of pages that contain the provided path.
• Asset changes that were not in a Documents folder path would not trigger re-indexing on changes.
• Asset metadata changes now trigger re-indexing of data.
• Asset binary file data would still be indexed even when the asset type had been flagged as non-indexabale at the CMS schema level.
• Synonym entries now support multi-word values.
• H1-H6 fields can be used as matching frag fields in the HiliteFields.xml configuration.
• The index.sbs file used for side-by-side re-indexing was not properly denormalizing the path values to the current read/write index location during test scenarios.
• Terms with underscores will be tokenized as a single term instead of separate terms (e.g., Spider_Man).
• Asset ID is now stored as a field value in the document index.
• Asset binary files published from a CMS 10.3 environment are now indexing based on timestamp change from the Assets.xml file in the published data set. A legacy asset indexing mode setting has been added to support content from CMS 10.2 and below.
• Asset descriptive metadata is returned in search results.
• Asset metadata list items are indexed in a single field. Each list item value is delimited with an ellipses within this single field.
• Fixed an issue with search implementations in a DSS where permission to the index folder location would be locked, resulting in an unresponsive DSS.
• For implementations that are indexing two different publishing target data sets, the asset metadata would not be indexed for the second source in the configuration list.
• Searches against the API using q as a parameter would return broken results. The q parameter is not a valid and will be ignored.
• Added the setting ContentTermSizeLimit (default value: 50) for spellchecker source configuration file in order to set a max limit of characters per field to index. This prevents large indexing times for large sources of content.
• Content would not be indexed on pages that contained List, Link, or Linkset elements and were set to expand on publish. To support this change in index behavior, the IGX_Presentations and LingualMaps elements are ignored during indexing.
• Categories Stats count of associated indexed items would not match the count of search results filtered on the same category ID.
• External asset metadata from CMS 10.3 published content would not be picked up by the indexer.
• The search query analyzer would not pass in hyphenated terms to a search query; instead, it split on the hyphenated term.

InSite Search 2.12.29 - March 28, 2019

• Added side-by-side re-indexing, which allows InSite Search to create a new index on configuration changes that require a full re-index. During re-indexing, InSite Search will continue to serve search results.
• Added the indexingQueueCapacity configuration in search.config to limit excessive memory use by queuing InSite Search indexing tasks.
• Added sample files, containing wrappers for use with DEX-based implementation projects, in the InSite Search DEX NuGet Package.
• InSite Search Analytics will now track all queries conducted against the site, regardless of whether the term searched produces results counts or not.
• Added Azure Application Insights custom metrics for InSite Search. Refer to DSS Custom Metrics with Azure Application Insights for more information.
• Added the additionalquery parameter to DEX search components, which allows for passing additional Lucene queries to a DEX search implementation.
• To reduce scenarios where logging would consume disk space, low-level Lucene logs are now disabled by default. They can be re-enabled via Search.config setting OmitLuceneMessagesLog to false (boolean, defaults to true).
• Added a new search parameter, excludesuggests (boolean, defaults to false), to enable/disable automatic search suggestions at query time. Note that this parameter assumes that the Search.config setting IncludeSpellcheckSuggestionsInQueryBuilding is enabled.
• Added a new configuration to SpellcheckerSource.config, ContentTermsCollectionLimit, which sets the top number of returned spell-checked terms instead of returning all.
• Added support in custom search implementations to exclude fields from constructed queries based on their CMS Page Element name. This is initial groundwork for future enhancements around improving the exclusion logic and configuration in InSite Search.
• Addressed an issue where SiteCrawler search sources would re-index pages more than once on repeated re-index cycles.
• Addressed an issue where multiple indexing readers were queueing that caused delays in index writing, resulting in stale search content.
• Site Crawler profiles can now be configured to limit indexing of pages based on a URL prefix match via the urlRestrictionPrefixes setting. This setting supports a comma-separated list of prefixes for a given profile.
• Added a new boolean setting, caseInsensitiveUrlMatch (boolean, defaults to false), to Site Crawler configuration that will prevent URL links to the same page with different casing from being indexed as unique documents in the search index.
• Recycling the application pool would sometimes result in no data being returned from search results.
• Fixed an issue where Spellchecker indexes would duplicate index entries instead of flushing and updating the entries in the index.
• Added additional logging to indicate whether indexing is enabled or disabled.
• CMS Link Elements to Document Assets would index its path value as the asset ID value. This has been fixed, and the expanded path to the asset is now indexed.
• Addressed an issue where custom search implementations that used a trailing wildcard to construct synonym searches would not return synonym results.

InSite Search 2.11.23 - September 12, 2018

• Added additional logging to indicate start and end of batch processing operations during indexing.
• Synonyms configuration now resides in a separate configuration XML file. Existing synonym entries will be migrated to this new format on upgrade to InSite Search 2.11.x release. This file can be configured as relative to the DSS application or as an absolute path to a file on the server. Customers using CMS 10+ can leverage this feature by managing their synonyms file as an Asset to be updated and published via the CMS. Further information on this feature can be found here.
• Added functionality for Site Crawl to ignore crawling of URLs that match configured querystring patterns.
• The Search.config Ingeniux.Runtime.DssContentSearchSource class name is supported in the code. Customers upgrading from InSite Search 2.9.x or below to 2.11.x are no longer required to update their Search.config to reflect the Ingeniux.Runtime.Search.DssContentSearchSource class name that was introduced in Insite Search 2.10.
• Added a configuration for Spellchecker Source configuration to index terms directly from the main content index for use in spellcheck/search suggest implementations.
• Added enhancements to the query engine via improved fuzzy matching for InSite Search implementations that utilize Search Suggest.
• Added a configuration option for HTML Search Sources to respect canonical URL entries. This results in duplicate pages being indexed if both pages have the same canonical URL value in their HTML.
• Added a new Simple Query configuration option, which simplifies search queries against a single field of terms from all other indexed fields for a document for improved search performance. This feature is disabled by default and can be enabled in Search.config. Customers who have implemented custom search implementations and wish enable this feature may need to adjust any custom queries towards this new field within their controllers. Refer to the SimpleQuery attribute description to enable this feature.
• Added configuration options to support indexing of Asset metadata from CMS 10 published content (metadataAssets_prefixes and metadataAssets_types).
• Fixed an issue where hyphenated search terms would cause a stack overflow in configurations where wildcard and Search Suggest were enabled.
• Fixed an issue where duplicate document entries would appear in Site Crawler search sources due to links for both HTTP and HTTPS being crawled for the same site.
• Fixed an issue where the HTML Site Crawler was unable to crawl websites residing on servers with TLS 1.0/1.1 disabled.
• Fixed an issue where Search Sources configuration values on a DEX search component would not be read in for a search. Search Source values will now allow filtering based on search source. This can also be overridden by providing the sources querystring parameter as well.
• Fixed an issue where matching fragment fields due to limitation in Lucene returning only the first 51,000 characters on a search result set.
• Fixed an issue with the _UNIQUEID_ field value unnecessarily containing the protocol identifier for Site Crawl indexed content.
• Fixed an issue where the Robots meta tag would not be respected during HTML Site Crawl if it was not entered in lowercase on the page.
• Fixed Asset Elements on pages published from CMS 10.1 being indexed as their asset ID rather than their full path due to a change in the RTAPI. Now the full path to the asset will be indexed as long as the asset is marked for publish for the search source.
• Fixed an issue where the Indexable attribute on a page schema's element was not registering when InSite Search was set to only index Indexable fields via the OnlyIndexSearchables custom setting.
• Fixed an issue where DEX Search Components configured with specific search sources were returning results from all search sources within an index.

InSite Search 2.10.14 - April 3, 2018

• Breaking Change: Customers preparing for upgrades to CMS 10.1 will need to make several changes to their InSite Search DSS projects, depending on their implementation. More information can be found on the following article here.
• Upgrading a Dynamic Site Server project from CMS 9 to CMS 10 will also include this latest version of InSite Search. Customers upgrading to CMS 10 will also need to upgrade to the latest InSite Search DEX - 10 package for their project, and to to update any DEX Search Schemas as well.
• Feature - InSite Search document indexing - v10 enhancements.
• Feature - HtmlSiteSource - read from meta tags to attempt to populate common elements that may not be present on page at index time.
• Feature - Options to parallel process pages and document, for both service and DSS.
• Feature - Honor settings for robots in meta tag or in robots.txt - nofollow, noindex, disallow.
• Feature - Add partial field name support for list of fields in HiliteFields.xml.
• Feature - Expose DocId on SearchResultItem.
• Fixed - Hilitier Tags can be cut off when using the HighlightFragSizeLimit.
• Fixed - InSite Search for a CMS 10 DSS throws error related to DynamicExecuteHelper.
• Fixed - URL field is empty.
• Fixed - Upgrading InSite Search Nuget packages causes cvshelper error.
• Fixed - Stemming YSOD - Indexing doesn't complete.
• Fixed - Default keymatchsource.config specifies an incorrect keymatch folder name.
• Fixed - _document_ type returns no UniqueID in XML output.
• Fixed - Default SiteCrawlerSource.config contains test data.
• Fixed - Referenced assets on a document component are still indexed as a standalone document in Lucene.
• Fixed - Pages with Start Date or End Date values will return based on local server time instead of UTC time.

InSite Search 2.9.8 - January 8, 2018

• This is the first release to support CMS 10. Upgrading a Dynamic Site Server project from CMS 9 to CMS 10 will also include this latest version of InSite Search. Customers upgrading to CMS 10 will also need to upgrade to the latest InSite Search DEX - 10 package for their project and also need to update any DEX Search Schemas as well.
• Feature - Added the QueryLuceneDocId attribute to search result sets. This value reflects the document ID in Lucene for the particular search result item.
• Fixed - CMS pages that were given Start/End Date and Time values were filtered incorrectly based on local server time rather than calculating on the original UTC time for the document in the search result index. This is now corrected, and search results will calculate the UTC time value to determine filtered results.

Insite Search 2.8.15 - July 27, 2017

• Feature - Added configuration IncludeComponentContentInPage option in Search.config to support expansion of referenced components and index them as fields on their source page.
• Feature - Added parameter to exclude xID and children of the xID from search results (ex_roots). DEX Search Navigation component now has equivalent field "Exclusion Roots."
• Feature - Added configuration HighlightFragSizeLimit option in Search.config to limit total length of matching fragments.
• Feature - Added configuration DedicatedHighlightFragField option in Search.config to declare an override field to return in place of matching fragments.
• Fixed - Double stemming would occur on synonym term searches for certain word pairings in synonym configuration.
• Fixed - Filter by Locale would cause Document assets to not return for DSSSearchSource library types. Document assets will now have locale field added at index time, with values of all discovered locales for the publishing target associated to the field.
• Fixed - Locale filter would also highlight locale values in matching fragments. Resolved this issue, which also resolved previously reported issue of 1 being highlighted in matching fragments as well.
• Fixed - Values were being normalized twice and resulted in invalid Synonym values.
• Fixed - Stemming analyzer would treat hyphens in locale values as a value to split on during tokenization.
• Fixed - Documents do not have /documents/ included in path field at index time if settingsFile has parent directory traversal in path.

InSite Search 2.7.8 - June 29, 2017

• Reverted fix implemented in 2.6.12 for highlighting 1 for some queries, as it was causing the character to be dropped in matching frags during certain queries.
• Fixed - SortBy parameter in API would not sort on field names that started with an underscore.
• Added the ancestors parameter, which will limit returned search results to only child pages of a provided xID. Supports multiple ancestor xIDs via comma-delimted list e.g. ?ancestors=x12,x24

InSite Search 2.6.12 - May 26, 2017

• Feature - InSiteSearch allows set weight based on specified facet values.
• Feature - Sanitize config files/errant Dev test files during final build and package process.
• Feature - Add configuration option to exclude file types from being indexed or set specific document paths only.
• Feature - Include Score in SearchResultItem object; Make MatchingFrags property deferred execution.
• Feature - Add ability to refer to inclusive list of specified fields to be returned in matching frags results.
• Feature - Create an index field to track filetype extensions for indexed documents.
• Feature - Add configuration option for index location for Analytics.
• Feature - Enable tail wildcard to the search query.
• Feature - Ability to define specific fields to construct search query.
• Feature - Add configuration to Search.config for anything that relies on \Config at root of DSS/External Search.
• Fixed - Default sorting for search navigation component and external service is inconsistent.
• Fixed - Match frags highlighting 1 for some query terms.
• Fixed - Documents being partially indexed into Lucene.
• Fixed - Duplicate document asset entries in my result set.
• Fixed - Error building terms dictionary when multiple small incremental publishes are conducted in the middle of dictionary build operation.
• Fixed - Site crawler is pulling in embedded CSS into the matchfrags.
• Fixed - Improve Score Intelligence for InSite Search.
• Fixed - Search Highlighter highlights all schema names.
• Fixed - SiteCrawlerSource.config by default should have a cycleunit = week.
• Fixed - Error writing/accessing index in a Search enabled DSS due to "Lock obtain timed out: NativeFSLock" error.
• Fixed - Applying SortBy parameter returns NaN within the Score element tag.
• Fixed - Indexing location has been change from the default location for external service.

InSite Search 2.5.5 - May 2, 2017

• Feature - Search Crawler feature to add in a start time and hourly intervals.
• Feature - Add stemming to Synonyms.
• Feature - Allow DEX Search components to not require a terms value to return results.
• Feature - Add Category Stats to Search Navigation DEX Component.
• Fixed - URL parameter site=[value] (i.e., search profiles) is case sensitive.
• Fixed - Expose batch size configuration for Search Suggest and Keymatch indexes.

InSite Search 2.4.13 - April 6, 2017

• Feature - Add additional unit/value options for Site Crawl Configuration.
• Feature - Change deletion behavior for Site Crawl during a recrawl operation.
• Fixed - DSS projects configured with Site Crawl are not crawling external URLs, no site crawl log generating.
• Fixed - Setting Sitecrawl to a non-trailing slash URL results with crawling duplicate URL.
• Fixed - Site Crawl will fail and prevent next Site Crawl from occurring.
• Fixed - Site Recrawl is adding new documents to the collection instead of updating existing entries.
• Fixed - URLs with upper casing are removed from the index.

InSite Search 2.3.10 - February 20, 2017

• Feature - Add ability to search against and index while indexing is disabled.
• Fixed - All fields related to ancestry is not indexing.
• Fixed - UpdatedTime field is not indexing.
• Fixed - Error processing Dynamic Execute:Could not load file or assembly 'DynamicExecuteHelper, Version=9.0.470.0.
• Fixed - Styling on failed login page is broken.
• Fixed - catsLogic parameter should be normalized to lowercase.
• Fixed - Error in log: Cannot write to a closed TextWriter.
• Fixed - Cannot pull in a previously excluded schema type.
• Fixed - Service call errors occurring in Search Configuration External service.
• Fixed - No category or type stats in results set.
• Fixed - No result when searching for word containing '&' symbol.
• Fixed - MUST logic for terms make any search on term contains - returns no results.
• Fixed - Custom facets stats not in results set.
• Fixed - Angular 2 does not initialize for external service.
• Fixed - Assembly bindings for ingeniux.search and ingeniux.support is a version behind for service.
• Fixed - Error on index: Could not initialize IntranetPublicContent instance of DssContentSearchSource: Input string was not in a correct format.
• Fixed - H6 tags are not pulled in by site crawler as a field into the index.
• Fixed - Error setting up indexing source SupportPubliccontent: Could not load file or assembly 'Ingeniux.Search, Version=2.0.4.0, Culture=neutral, PublicKeytoken=4a949968764df20e' or one of its dependencies.

InSite Search 2.2.8 - December 28, 2016

• Feature - Add exclusion by xID based on NoIndex boolean value set on the xID.
• Feature - Implement toggle checkbox for Structured Grouping in result set data.
• Fixed - Non-list-elements with duplicate names do not get returned.
• Fixed - Index incorrectly parses E-mail addresses if "at" symbol is followed by a numeral.
• Fixed - 'Display Fragments Size' field value does not change the size of value for remote DEX.
• Fixed - Duplicate keyterm values within CSV and publish content result with returning CSV results only.
• Fixed - MUST_NOT is an available option in DEX Navigation Component for Cross Facet logic.
• Fixed - DEX local search component defaults to MUST.
• Fixed - Category associations are not updating based off of result set.
• Fixed - Pagination on search navigation DEX YSODs.
• Fixed - Error processing Dynamic Execute: Could not load file or assembly 'DynamicExecuteHelper, Version=9.0.470.

InSite Search 2.1.10 - November 18, 2016

• Feature - New Search Navigation DEX Component and RESTful services.
• Feature - Allow customErrors attribute to enable debug logging for Insite Search error output.
• Fixed - InSite Search Configuration UI is completely broken for External Service.
• Fixed - Stack trace is always returned in Search Web API Controller.
• Fixed - Search return & Search facets are both hardcoded to max 10,000 results.
• Fixed - DEX search local component - no results returned when enabling "Exclude documents from search results."
• Fixed - DEX local search component defaults to MUST.
• Fixed - No results for search suggestions.
• Fixed - DEX local search component category MUST_NOT.
• Fixed - Enabling "Exclude documents from search results" excludes assets from returning.
• Fixed - Page parameter does not paginate.
• Fixed - Search Suggest returns duplicate word values.
• Fixed - Search GetTermsWithFrequency method Performs very slowly regardless of returned result size.
• Fixed - Search Suggest component schema does not have a default value for Search Result Order.
• Fixed - xID with NoIndex value toggled is still returned in terms search results.
• Fixed - Schema for new DEX Navigation Component missing from NuGet package.
• Fixed - Missing bin\DynamicExecutes from DSS project.
• Fixed - DEX Navigation component not returning results.
• Fixed - No results returned for DEX Navigation component if Ancestor is set to Home xID.
• Fixed - GetFullTextTermQuery is missing overload with original signature
• Fixed - MUST_NOT is an available option in DEX Navigation Component for Cross Facet logic.
• Fixed - Remove note from readme.txt.

InSite Search 2.0.40 - October 24, 2016

• Feature - NuGet package for DEX components for search.
• Feature - Locales parameter has been added to DEX
• Feature - Add an attribute to DEX Component Schema to indicate component version.
• Fixed - Queried Katakana terms return results with single character matches.
• Fixed - Half width Katakana (extensives) characters are not searchable.
• Fixed - Linkset xIDs do not get indexed.
• Fixed - Internal link element indexes link URL name as field value opposed to the fully expanded structured URL.
• Fixed - catsfreq missing help API.
• Fixed - Search profiles sources shipped with default Search.config.
• Fixed - Keymatch help API is inheriting from parent.
• Fixed - Enabled "Include Categorization Stats" should return all category associations.
• Fixed - InSite Search returns HTML tag brackets in matchingFrags property of search result items.
• Fixed - Enabling "Include All Fields" should result with true.