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.
Bundle handling has multiple issues stemming from the use of delta's to store exclusions, and bundle labels to store available bundle types.
- Adding, removing or renaming a bundle will break the exclusion list, as the list is stored according to the order in which bundles appear (delta)
- Adding or removing bundles from the search index has the same effect
- Duplicate bundle names in different entity types will be filtered out, leading to unpredictable results
- Removing bundles can lead to an error being thrown during searching, which will flag search as being unavailable, and turn search off
Patch coming...
Comment | File | Size | Author |
---|---|---|---|
#4 | 2224325-4-broken-bundle-info.patch | 20.3 KB | xtfer |
Comments
Comment #1
xtfer CreditAttribution: xtfer commentedComment #2
xtfer CreditAttribution: xtfer commentedComment #3
xtfer CreditAttribution: xtfer commentedComment #4
xtfer CreditAttribution: xtfer commentedThis patch does the following:
Providing in an upgrade path is tricky, since the existing data is not entity_type aware, may have confused bundle keys, and may well be incorrect anyway. The best upgrade path is to inform users they need to check and redo their exclusion settings (if they have any), so I've added some helpers for that.
I was unable to determine how to apply subqueries to filter by bundle name AND entity type (or site hash, for that matter), so Ive just left bundle filters at query time pretty much as they are. More complex filtering may be quite difficult due to the nature of Solr filters, however the data is all there, so someone with better Solr query chops than me may be able to resolve that now.
Comment #5
xtfer CreditAttribution: xtfer commentedProbably related: #1909668: Select specific sites to search in a multisite search environment