You are here

Home » API reference » Extended search page 7

README.txt in Extended search page 7

Same filename in this branch
  1. 7 README.txt
  2. 7 ext_search_admin/README.txt
  3. 7 ext_search_node_ref/README.txt
Extended Search Page
--------------------

The goal is to provide a page like the default "Find content" but on top of scalable technology for sites with huge amounts of nodes.
So this module support solr and mysql through Search API and uses entity metadata to discover objects fields.

The module uses the search api pages (see below).

Features
--------

 - fulltext index are searched through a text input 
 - non fulltext index can be used as filters (like in the content page) in the search page form
 - you can choose a form widget for each filter
 - you can specify default value for filters (even if filter is not displayed)
 - each search page can have a dedicated search form block
 - thoses widgets are shown in the search page and managed by URL (vs session for SEO)
 - suported fields : boolean, date with date_range, node_reference (with mono term select)
 - widgets support can be extended by a hook


Test
----

I've done test against solr index.


TODO
----
Field/CCK widget integration for entity_reference (ie a lighbox node browser)


Requirement
-----------

Module search_api : http://drupal.org/project/search_api 
Module search_api_page


Mainterner
----------

David Berlioz aka quazardous
http://drupal.org/user/399916

File

README.txt
View source 
  1. 

  2. Extended Search Page

  3. --------------------

  4. 

  5. The goal is to provide a page like the default "Find content" but on top of scalable technology for sites with huge amounts of nodes.

  6. So this module support solr and mysql through Search API and uses entity metadata to discover objects fields.

  7. 

  8. The module uses the search api pages (see below).

  9. 

  10. Features

  11. --------

  12. 

  13.  - fulltext index are searched through a text input 

  14.  - non fulltext index can be used as filters (like in the content page) in the search page form

  15.  - you can choose a form widget for each filter

  16.  - you can specify default value for filters (even if filter is not displayed)

  17.  - each search page can have a dedicated search form block

  18.  - thoses widgets are shown in the search page and managed by URL (vs session for SEO)

  19.  - suported fields : boolean, date with date_range, node_reference (with mono term select)

  20.  - widgets support can be extended by a hook

  21. 

  22. 

  23. Test

  24. ----

  25. 

  26. I've done test against solr index.

  27. 

  28. 

  29. TODO

  30. ----

  31. Field/CCK widget integration for entity_reference (ie a lighbox node browser)

  32. 

  33. 

  34. Requirement

  35. -----------

  36. 

  37. Module search_api : http://drupal.org/project/search_api 

  38. Module search_api_page

  39. 

  40. 

  41. Mainterner

  42. ----------

  43. 

  44. David Berlioz aka quazardous

  45. http://drupal.org/user/399916