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.
Based on #377270: Core search index not complete and a general desire among the infra team not to maintain the core search index for all nodes, we discussed just indexing project_issue nodes and their comments for use on the issue advanced search views. Most sites could just rely on the core search index (assuming it's complete), but for sites that are using something else for general search but still want issue views, we can provide this sub module for their needs. Damien is apparently finishing a first draft now, just starting an issue about it to track the code and progress.
Comment | File | Size | Author |
---|---|---|---|
#2 | 381554-project-issue-index.patch | 2.9 KB | Damien Tournoud |
#1 | 381554-project-issue-index.patch | 2.93 KB | Damien Tournoud |
Comments
Comment #1
Damien Tournoud CreditAttribution: Damien Tournoud commentedHere is a first shot. We will need to modify the default view for project_issue so that the correct index type ('project_issue', not 'node') is used if that module is enabled.
Comment #2
Damien Tournoud CreditAttribution: Damien Tournoud commentedOk, let's reuse the node namespace. Even if node search is on, conflicts should be minimal because those two are actually just doing the same thing, with a different scope (project_issues only for this module, all nodes for the node search).
Comment #3
dwwBased on a little chat with hunmonk, I renamed this, added a README, and committed to HEAD:
http://drupal.org/cvs?commit=175016
Deployed on d.o and it's working great.
Yay!