Go to file
Sean Harvey 4f58937636 Logging Solr communication exceptions as warnings
Before we didn't catch exceptions, the CMS would break when communication
errors with Solr occurred, this change will log those exceptions as warnings
so that creating new and publishing pages will continue gracefully.
2013-02-13 09:52:06 +13:00
_config BUG make bind_manipulation_capture call correctly 2012-07-19 12:09:44 +12:00
code Logging Solr communication exceptions as warnings 2013-02-13 09:52:06 +13:00
conf ENHANCEMENT Better spell checking default config and docs 2012-09-05 22:20:28 +02:00
docs Fixing missing backtick to indicate code formatting 2013-02-13 09:46:22 +13:00
tests Merge pull request #6 from silverstripe-big-o/ignore-empty-fields 2012-11-01 14:27:31 -07:00
thirdparty Import first version of fulltextsearch module 2011-05-02 16:33:05 +12:00
README.md removing experimental notes in docs 2013-02-13 09:48:26 +13:00
_config.php BUG make bind_manipulation_capture call correctly 2012-07-19 12:09:44 +12:00
composer.json Add composer file 2012-11-03 12:31:41 +13:00

README.md

FullTextSearch module

Adds support for fulltext search engines like Sphinx and Solr to SilverStripe CMS.

Maintainer Contact

  • Hamish Friedlander <hamish (at) silverstripe (dot) com>

Requirements

Documentation

See docs/README.md

TODO

  • Get rid of includeSubclasses - isn't actually used in practice, makes the codebase uglier, and ClassHierarchy can be used at query time for most of the same use cases

  • Fix field referencing in queries. Should be able to do $query->search('Text', 'Content'), not $query->search('Text', 'SiteTree_Content') like you have to do now

    • Make sure that when field exists in multiple classes, searching against bare fields searches all of them

    • Allow searching against specific instances too

  • Make fields restrictable by class in an index - 'SiteTree#Content' to limit fields to a particular class, maybe 'Content->Summary' to allow calling a specific method on the field object to get the text

  • Allow following user relationships (Children.Foo for example)

  • Be clearer about what happens with relationships to stateful objects (e.g. Parent.Foo where Parent is versioned)

  • Improvements to SearchUpdater

    • Make it work properly when in-between objects (the A in A.B.Foo) update

    • Allow user logic to cause triggering reindex of documents when field is user generated

  • Add sphinx connector

  • Add generic APIs for spell correction, file text extraction and snippet generation

  • Better docs