integrate search with the Django-CMS is Haystack, however it is not officially supported. 3.6.1 Haystack If you go the Haystack way, you’ll need a search_indexes.py.Haystack doesn’t care if it’s in the same app django.conf import settings from django.utils.translation import string_concat, ugettext_lazy from haystack import indexes, site 50 Chapter 3. Extending the CMS django cms Documentation, Release 2.1.5 from

1.7.4 Haystack If you use Haystack as your projects search engine, here’s an example of how you can have Django Q take care of your indexes in real time using model signals: # Real time Haystack indexing sender, instance, save=False) # turn off result saving to not flood your database # tasks.py from haystack import connection_router, connections def index_object(sender, instance): # get possible backends

1.8.4 Haystack If you use Haystack as your projects search engine, here’s an example of how you can have Django Q take care of your indexes in real time using model signals: # Real time Haystack indexing flood your database 28 Chapter 1. Features Django Q Documentation, Release 0.5.3 # tasks.py from haystack import connection_router, connections def index_object(sender, instance): # get possible backends

sending task from the report generation function and to report on possible failures. 1.9.4 Haystack If you use Haystack as your projects search engine, here’s an example of how you can have Django Q take care using model signals: 32 Chapter 1. Features Django Q Documentation, Release 0.6.4 # Real time Haystack indexing from .models import Document from django.db.models.signals import post_save from django sender, instance, save=False) # turn off result saving to not flood your database # tasks.py from haystack import connection_router, connections def index_object(sender, instance): # get possible backends

1.9.4 Haystack If you use Haystack as your projects search engine, here’s an example of how you can have Django Q take care of your indexes in real time using model signals: # Real time Haystack indexing sender, instance, save=False) # turn off result saving to not flood your database # tasks.py from haystack import connection_router, connections def index_object(sender, instance): # get possible backends

13.4 Haystack If you use Haystack as your projects search engine, here’s an example of how you can have Django Q take care of your indexes in real time using model signals: # Real time Haystack indexing sender, instance, save=False) # turn off result saving to not flood your database # tasks.py from haystack import connection_router, connections def index_object(sender, instance): # get possible backends

13.4 Haystack If you use Haystack as your projects search engine, here’s an example of how you can have Django Q take care of your indexes in real time using model signals: # Real time Haystack indexing flood your database 1.13. Examples 43 Django Q Documentation, Release 0.7.11 # tasks.py from haystack import connection_router, connections def index_object(sender, instance): # get possible backends

13.4 Haystack If you use Haystack as your projects search engine, here’s an example of how you can have Django Q take care of your indexes in real time using model signals: # Real time Haystack indexing sender, instance, save=False) # turn off result saving to not flood your database # tasks.py from haystack import connection_router, connections def index_object(sender, instance): # get possible backends

10.4 Haystack If you use Haystack as your projects search engine, here’s an example of how you can have Django Q take care of your indexes in real time using model signals: # Real time Haystack indexing flood your database 1.10. Examples 41 Django Q Documentation, Release 0.7.10 # tasks.py from haystack import connection_router, connections def index_object(sender, instance): # get possible backends

13.4 Haystack If you use Haystack as your projects search engine, here’s an example of how you can have Django Q take care of your indexes in real time using model signals: # Real time Haystack indexing sender, instance, save=False) # turn off result saving to not flood your database # tasks.py from haystack import connection_router, connections def index_object(sender, instance): # get possible backends