Since vocabularies and their terms are such an important part of Drupal, not being able to search them looks like a bug. OTOH, since it has been missing all that time, maybe it's a feature ?

The suggested patch adds this feature.

Comments

chx’s picture

Version: 6.x-dev » 7.x-dev
Category: bug » feature
Status: Active » Needs review
birdmanx35’s picture

This still applies to HEAD, although there is some offset:

$ patch -p0 < taxonomy.module_44.patch
(Stripping trailing CRs from patch.)
patching file modules/taxonomy/taxonomy.module
Hunk #1 succeeded at 1311 (offset 157 lines).

pancho’s picture

StatusFileSize
new1.2 KB

Rerolled against HEAD with some minor changes.

fgm’s picture

Considering the talks about terminology regarding taxonomy, maybe we need to change "Tags" to something more consistent with uses elsewhere in Drupal, like "taxonomy", "terms", "vocabularies" ?

pancho’s picture

I guess, "taxonomy terms" would be correct. This is a moving target though.

BlakeLucchesi’s picture

This works as a quick fix to allow the savvy user to search through categories that are on a website but at least to me, I'd imagine people wanting to be able to have their taxonomy term pages show up alongside normal search results.

Thus, instead of saying: Do you wish to search for a category that we may have on our website? We present them with category matches when they search using the generic search form. If we really care about the user experience, this is something that we must address and implement (as well as support to link to views and panel pages).

Just my 2cents.

-Blake

catch’s picture

Yeah. It makes sense for user searches to be separate, but taxonomy terms are (often) used as high level pages.

Say you have a taxonomy term for 'news', aliased as 'news' - it currently won't appear anywhere in a search for that word.

It'd be useful to have a straight search for terms on admin/content/taxonomy though.

robertdouglass’s picture

Component: search.module » taxonomy.module
Status: Needs review » Needs work
StatusFileSize
new1.23 KB

Rerolled and renamed tags to taxonomy since we recently got rid of Categories as a taxonomy synonym.

I'm not keen on the patch as it is, though. It doesn't go far enough to be really useful. I'd want the vocabulary names and the term synonyms to be in there, too, but you won't get that quite as easily just relying on the taxonomy module's API. Plus, if we put this in the taxonomy module as is, it forces people to have a taxonomy search tab. I'd rather have it in its own module so I can turn it off if not needed. The alternative to this is modifying the search module in a way that lets one opt out of search implementations.

robertdouglass’s picture

Title: Search does not search taxonomy terms » Implement taxonomy term search

New title.

catch’s picture

catch’s picture

Anonymous’s picture

Version: 7.x-dev » 8.x-dev

This is a good feature request that requires more thought than we can give it before D7 code freeze-for-real. Fieldable terms changes a lot.

It would be good to try this in contrib in the meantime for D7.

catch’s picture

Version: 8.x-dev » 7.x-dev
hass’s picture

+

jhodgdon’s picture

Version: 7.x-dev » 8.x-dev

This is a feature request. D7 is feature frozen, so moving this to Drupal 8.

The proposal here is to add a new search tab/type for taxonomy search.

Taxonomy terms are (hopefully, they were in d6 anyway) already indexed with nodes, by the way.

Hetta’s picture

If you have a botany site ... (I do), you can have thousands and thousands of taxonomy terms which aren't found in any node.
Taxonomy search is definitely a must-have, and better sooner than later.

Anonymous’s picture

Hetta: It's possible to offer a perfectly adequate taxonomy term search in contrib, which would be a fine place to develop a feature that could be merged into Drupal 8. If you're at Drupalcon SF, I can help you get started on such a module. It really would not be very hard!

jhodgdon’s picture

Indeed, if we had a D7 taxonomy search contrib module, I would love to spearhead getting it into D8 core. And I agree with bangpound that the hooks are there to do a taxonomy search module.

Hetta’s picture

The only tax search module I've found is still in d5 ... with a patch that puts it at d6. I've downloaded that but haven't yet given it a shot.

http://drupal.org/project/taxonomy_search
http://drupal.org/node/261903

Sorry, can't currently attend drupalcons.

bala.d’s picture

fgm’s picture

@bala.d: Not really relevant: taxonomy_manager is an admin UI for taxonomy, not a search feature you would want to put in the hands of site users.

asb’s picture

Related feature request for the Seach by page module (D6): #988736: Search Taxonomy terms

Jeff Burnz’s picture

For D7 there is http://drupal.org/project/custom_search which goes way further than simple taxonomy search but maybe a solution for folks who need a solution now.

scotthorn’s picture

Hi, I've been working on a module that has basic taxonomy term searching functionality for D7. It may be of help to people looking for an immediate solution:
http://drupal.org/project/term_search

...I'd imagine people wanting to be able to have their taxonomy term pages show up alongside normal search results.

I agree with BlakeLucchesi that it would be nice to have term searches show up alongside nodes and other entities. This feature is not currently included in my module.

mfb’s picture

Seems what is needed is entity search. With one result set searching all entities (or, at least all entities enabled for that search index). Then users could drill down within those results to only search particular entities.

Taxonomy term pages are often built out as key landing pages on a site, and it is really quite bizarre if they do not appear in search results - or require users to run a separate search.

jibran’s picture

Title: Implement taxonomy term search » Implement SearchPlugin for taxonomy
Version: 8.0.x-dev » 8.1.x-dev
Issue summary: View changes
Status: Needs work » Postponed

Marking #1964458: Implement hook_search_execute() for terms duplicate of this. This is a plain feature request so moving it to 8.1.x

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.0-beta1 was released on March 2, 2016, which means new developments and disruptive changes should now be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.0-beta1 was released on August 3, 2016, which means new developments and disruptive changes should now be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.0-alpha1 will be released the week of January 30, 2017, which means new developments and disruptive changes should now be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.0-alpha1 will be released the week of July 31, 2017, which means new developments and disruptive changes should now be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.1.x-dev

Drupal 8.9.0-beta1 was released on March 20, 2020. 8.9.x is the final, long-term support (LTS) minor release of Drupal 8, which means new developments and disruptive changes should now be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

Status: Postponed » Postponed (maintainer needs more info)
Issue tags: +stale-issue-cleanup

Thank you for sharing your idea for improving Drupal.

We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

fgm’s picture

Status: Postponed (maintainer needs more info) » Active

Although I submitted a patch some years ago, I think we should now stop considering the need for a such an entity-specific search plugin and rather make indexed search available to all entities, with the ability for each entity type to have specific extra behaviours like the interpretation of tag relationships in the case of taxonomy.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.