Go to file
Sam Minnee 4b51393e01 Don't rely on MySQL ordering of index->getAdded()
MySQL is more reliable in its output ordering of elements where the order doesn't matter.
PostgreSQL is not.  This meant that this test "accidentally passed" on MySQL and failed on
PostgreSQL.  The sort function resolves this.
2014-02-14 11:32:24 +13:00
_config API Move SearchUpdate queue handling to DIed processor, add QueuedJob support 2013-07-25 14:28:10 +12:00
code Remove config output 2014-01-17 09:28:50 +13:00
conf/solr Include default lookup for custom libs in ./lib 2014-01-16 13:54:40 +13:00
docs/en MINOR: Update broken tutorial link 2013-11-21 09:31:53 +13:00
tests Don't rely on MySQL ordering of index->getAdded() 2014-02-14 11:32:24 +13:00
thirdparty API Move local solr to own repo 2013-11-08 16:28:51 +13:00
.travis.yml Make tests run 2013-09-11 14:35:01 +12:00
LICENSE Create LICENSE 2013-09-02 11:42:29 +02:00
README.md Fixing SS 3.1 support. Changing minimum requirement to 3.1 as a result. 2013-04-03 15:43:08 +13:00
_config.php BUG make bind_manipulation_capture call correctly 2012-07-19 12:09:44 +12:00
composer.json API Move local solr to own repo 2013-11-08 16:28:51 +13:00

README.md

FullTextSearch module

Build Status

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/en/index.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