Aricie LuceneSearch release notes

Version 1.8.1

• Important fix: Added a DNN package registration for the Lucene.Net library during install in order to prevent its deletion when uninstalling LuceneSearch
• Fix: Patched the autocomplete to work with v1.10 of jQuery.UI
• Fix: SearchSkinObject now fails less embarrasingly when something goes wrong with the LuceneSearch settings
• Evolution: Provider for DNN 7.1 is a bit more efficient by not fetching settings for each module

Version 1.8.0

DotNetNuke 7.1 support: since the DNN 7.1 release there is a new search system to use. We didn't handle this system until now because we couldn't see any way to plug into the new architecture. After some brainstorming we decided to make LuceneSearch compatible with 7.1 in the simplest way possible: by using our own provider architecture. Since plugging into DNN is no longer possible LuceneSearch on a DNN 7.1 will add its own scheduled indexation task. Please review scheduled tasks in order to disable the native DNN 7.1 one if it is no longer necessary.

Thanks for reporting any problems or bugs you may encounter.

• DNN 7.1 search architecture supported
• Now using Lucene.Net library 3.0.3 (.Net 4 mandatory)
• Installation process modified to take into account the new visualisation mode since DNN7.x

Version 1.7.6

• Issue 1061 corrected: search now resets page number correctly
• Added configuration to the field system to let providers define their own analyzers
• Html5 error corrected: self-closing non void elements are not handled nicely in html5
• Badly uninstalled modules shouldn't cause any more problems
• Skin object webservice and script resolution now uses the application root

Version 1.7.5

• Huge performance upgrade for main LuceneSearch engine: loading the index now only loads necessary fields which decreases the memory footprint and cpu hogging
• Huge performance upgrade for StandAloneDocumentProvider

Version 1.7.4

• Fix: highlights were not working with prefix search when more than one item was found in the index
• Fix: the searched field configuration was reset to the default values when the user changed it
• Fix: mono-thread indexation wasn't working correctly on multiple portals

Version 1.7.3

• Fix: Only one search engine thread indexing and storing data in the Lucene index can now be running at the same time, since some versions of DotNetNuke's scheduler can launch the same task multiple times
• Fix: DMX Provider only returns items depending on the root path of the current DMX module analyzed
• Changes to css files to narrow down selection when applying styles
• Sort from filters are now applied and processed correctly
• ImagePath added to all items to include custom image to every content
• NewsArticle provider upgraded to retrive categories and tags
• Documentation changed to PDF

Version 1.7.2

• Fix: search is correctly launched on [ENTER] for skinobjects using their link display (not icon)
• Fix: css for the search skin object can now be defined independently. The css rules have been moved to an independent css file (skinobject.css at the root of the module) and two properties have been added to the skinobject:
  • IncludeSkinObjectCSS is a boolean parameter that lets you control whether the skin object will automatically include the css. Defaults to false
  • SkinObjectCSS is a string parameter that stores the url (relative to your website or absolute) for the css to include if IncludeSkinObjectCSS is true
  If you were including the module.css directly for the skinobject, please note that you must now either include skinobject.css or use the setting to force its inclusion

Version 1.7.1

• Switched back to unique provider for both DNN6 and DNN7 to avoid dependency on the .net Framework V4 when working with DNN7
• Fix: icons for module actions now work correctly
• Fix: read-only templates resource file cause the templates not to be rendered
• Fix: module not working on version 5.x.x of DotNetNuke
• Fix: dead link to lucene syntax in the online documentation has been corrected
• Depends on Aricie.Shared 1.7.1

Version 1.7.0

Warnings about v1.7.0: if you are using some content-based templates or locale-based templates, you will have to transfer them to the new template system by hand. The upgrade process will take care of templates defined in the module settings but the way DotNetNuke handles resource files does not lend itself to the migration of other templates. If you have any question regarding the upgrade, please contact us.

• Fully compatible with DNN7
• New results template interface that lets the user edit all templates in the UI
• Based on Aricie.Shared 1.7: you must install Aricie.Shared 1.7 previous to installing LuceneSearch 1.7. Previous versions of Aricie.Shared will trigger an error during LuceneSearch v1.7

Version 1.6.2

• Results are now configured to filter result depending on the user's DNN permissions by default
• Fix : the search panel is correctly hidden depending on the configuration
• Fix: the auto-complete search on a child portal no longer returns the results from the parent portal.
• Fix: the backing fields that are not supposed to be seen by the user in the Search Behavior tab are now hidden

Version 1.6.1

• Corrects initialization of indexing folder at module start
• Default settings changed: search is not launched automatically without user input
• Default settings changed: when activated, the autocomplete tries to inject the jQuery.UI javascript and css it needs by default

Version 1.6.0

• Improved configuration UI: configuration screens have been reorganized and display contextual settings depending on your choices
• Bugfixes: Sorting and paging improved on both template and grid mode
• Speed optimisation on indexation