Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Hello, currently I am trying to implement apachesolr search on one of our sites. I've read a lot about it. As I thought display suite search will not make any additional node_load, but in fact it does. In this function ds_search_process_results inside ds_search.module. Why we need it? Maybe my settings are wrong? When I use search results display instead of teaser nodes are also loaded. I will attach my settings screenshots, thank you in advance.
I use apachesolr 7.x-1.6 and display suite 7.x-2.6.
| Comment | File | Size | Author |
|---|---|---|---|
| ds_search_config.png | 65.58 KB | Bogdan1988 | |
| apachesolr_search_page_config.png | 73.6 KB | Bogdan1988 | |
| active_search_modules.png | 88.52 KB | Bogdan1988 |
Comments
Comment #1
aspilicious CreditAttribution: aspilicious commentedThats by design.
I know why we need a node load because Display Suite renders view modes on full entity objects. For some sites this leads to performance issues and they need better/custom solutions. But for smaller sites this is perfectly ok.
I have managed to save a specific view mode into solr and fetch it out with custom queries.
But as I said, all custom solutions, nothing reusable for a project as display suite.
Comment #2
Bogdan1988 CreditAttribution: Bogdan1988 commentedI don't think that we need to decrease performance, especially in drupal. That's why I decided to create https://www.drupal.org/project/apachesolr_display module. I leave this comment to help other who will be faced same performance problems as I. Thank you.