CMS Management about silverstripe-solr-search

[Firesphere]

Fields to be indexed should not be CMS configurable.

It's too complicated and confusing for CMS users to even look at it. A better approach would be to define which classes should/could be indexed and have them listed with the fields that are indexed.

Problem:
Classes to be indexed can contain a lot of data that shouldn't be indexed

Solution:
Make the logical decision beforehand

[Firesphere]

This is still in progress. It's working for single-core search setups, but multi-core set-ups are a bit tricky, which would require a "virtual" object to contain the related things. WIP.

[Firesphere]

Current status is that it's too complex and/or fault intolerant, users can too easily break configurations.