upadted to 1.8
This commit is contained in:
+20
-19
@@ -105,8 +105,10 @@ IMPORTANT: Access checks
|
||||
specific search types, if available.
|
||||
|
||||
As stated above, you will need at least one other module to use the Search API,
|
||||
namely one that defines a service class (e.g. search_api_db ("Database search"),
|
||||
provided with this module).
|
||||
namely one that defines a service class (e.g., search_api_db ("Database search")
|
||||
which can be found at [3]).
|
||||
|
||||
[3] http://drupal.org/project/search_api_db
|
||||
|
||||
- Creating a server
|
||||
(Configuration > Search API > Add server)
|
||||
@@ -208,6 +210,12 @@ search_api_index_worker_callback_runtime:
|
||||
API will spend indexing (for all indexes combined) in each cron run. The
|
||||
default is 15 seconds.
|
||||
|
||||
search_api_batch_per_cron:
|
||||
By changing this variable, you can define how many batch items are created on
|
||||
a single cron run. The value is per index, so on a site with 5 indexes with a
|
||||
cron limit of 100 each, the default value of 10 will load and queue up to 5000
|
||||
search items in up to 50 batch items.
|
||||
|
||||
|
||||
Information for developers
|
||||
--------------------------
|
||||
@@ -221,9 +229,9 @@ Information for developers
|
||||
| For custom field types to be available for indexing, provide a
|
||||
| "property_type" key in hook_field_info(), and optionally a callback at the
|
||||
| "property_callbacks" key.
|
||||
| Both processes are explained in [1].
|
||||
| Both processes are explained in [4].
|
||||
|
|
||||
| [1] http://drupal.org/node/1021466
|
||||
| [4] http://drupal.org/node/1021466
|
||||
|
||||
Apart from improving the module itself, developers can extend search
|
||||
capabilities provided by the Search API by providing implementations for one (or
|
||||
@@ -231,7 +239,9 @@ several) of the following classes. Detailed documentation on the methods that
|
||||
need to be implemented are always available as doc comments in the respective
|
||||
interface definition (all found in their respective files in the includes/
|
||||
directory). The details for hooks can be looked up in the search_api.api.php
|
||||
file.
|
||||
file. Note that all hooks provided by the Search API use the "search_api" hook
|
||||
group. Therefore, implementations of the hook can be moved into a
|
||||
MODULE.search_api.inc file in your module's directory.
|
||||
For all interfaces there are handy base classes which can (but don't need to) be
|
||||
used to ease custom implementations, since they provide sensible generic
|
||||
implementations for many methods. They, too, should be documented well enough
|
||||
@@ -255,7 +265,9 @@ service class.
|
||||
The central methods here are the indexItems() and the search() methods, which
|
||||
always have to be overridden manually. The configurationForm() method allows
|
||||
services to provide custom settings for the user.
|
||||
See the SearchApiDbService class for an example implementation.
|
||||
See the SearchApiDbService class provided by [5] for an example implementation.
|
||||
|
||||
[5] http://drupal.org/project/search_api_db
|
||||
|
||||
- Query class
|
||||
Interface: SearchApiQueryInterface
|
||||
@@ -334,15 +346,6 @@ See the processors in includes/processor.inc for examples.
|
||||
Included components
|
||||
-------------------
|
||||
|
||||
- Service classes
|
||||
|
||||
* Database search
|
||||
A search server implementation that uses the normal database for indexing
|
||||
data. It isn't very fast and the results might also be less accurate than
|
||||
with third-party solutions like Solr, but it's very easy to set up and good
|
||||
for smaller applications or testing.
|
||||
See contrib/search_api_db/README.txt for details.
|
||||
|
||||
- Data alterations
|
||||
|
||||
* URL field
|
||||
@@ -391,14 +394,12 @@ Included components
|
||||
|
||||
- Additional modules
|
||||
|
||||
* Search pages
|
||||
This module lets you create simple search pages for indexes.
|
||||
* Search views
|
||||
This integrates the Search API with the Views module [1], enabling the user
|
||||
This integrates the Search API with the Views module [6], enabling the user
|
||||
to create views which display search results from any Search API index.
|
||||
* Search facets
|
||||
For service classes supporting this feature (e.g. Solr search), this module
|
||||
automatically provides configurable facet blocks on pages that execute
|
||||
a search query.
|
||||
|
||||
[1] http://drupal.org/project/views
|
||||
[6] http://drupal.org/project/views
|
||||
|
||||
Reference in New Issue
Block a user