Postponed
Project:
Drupal core
Version:
main
Component:
search.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Jan 2019 at 20:33 UTC
Updated:
1 Apr 2026 at 03:08 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
eli-tComment #3
saesa commentedI think you should create a view called search. You can Implements hook_preprocess_breadcrumb() to modify the breadcrumb but not to change the url.
Comment #4
saesa commentedYou have to modify this view, that is already created.


When you search in this view the breadcrumb is Home> Search.
Comment #5
saesa commentedAnd also change the current search block to an exposed block from the previous view.
Comment #9
jhodgdonThis problem with the breadcrumbs is actually in the Search module, not Umami theme.
The URL is correct, but the breadcrumbs are not.
Comment #10
jhodgdonTwo things:
a) Let me clarify about the URL.
If you are using the core Search module, the URL of each configured search page will be example.com/search/whatever_you_decide
So the Umami demo could choose a different suffix for the content search page. The default suffix of "node" comes from
core/modules/node/config/optional/search.page.node_search.yml
The Umami demo could have its own copy of this config file and change the "path" component to something like "content" so the URL would be example.com/search/content. It is not possible in the core Search module to make the path be just example.com/search, although if you go to that URL you will also get to the default search page, which will be the content search page.
We could also fix this in the core/modules/node config, which I think would be a good idea.
b) The breadcrumbs.
The breadcrumbs are:
1. On the search page itself, whether you are on example.com/search/node or example.com/search/user:
Home (points to example.com)
Search (points to example.com/search)
2. On the search help page:
Home (points to example.com)
Search (points to example.com/search)
Search (points to example.com/search/node or example.com/search/user, depending on if you are on the content or user search help page)
So the first "Search" breadcrumb is actually not incorrect. But the second one should have a different title -- either Content or User, so that if you are on the content search help page the breadcrumb would be Home > Search > Content, and on the user search help page it would be Home > Search > Users -- these would match the tabs shown on the Search page if you are logged in with permission to search both content and users.
c) The breadcrumb behavior described in (b) is the default behavior. However, in Umami it is even worse, because for some reason Umami adds another layer to the breadcrumbs.
So if you are on the search page and have not yet searched, the breadcrumb is
Home (points to example.com)
Search (points to example.com/search)
Search (not linked, same as page title)
And if you have done a search, it is:
Home (points to example.com)
Search (points to example.com/search)
Search for whatever you entered (not linked, same as page title)
And on the search help page it is:
Home (points to example.com)
Search (points to example.com/search)
Search (points to example.com/search/node or example.com/search/user, depending on if you are on the content or user search help page)
Search (not linked, and not the same as the page title for some reason -- the page title is currently Search help although that will be changing on #3086795: "Search help" link in search form is ambiguous and confusing)
So, this is a bug in both the core Search module and the Umami Demo profile.
Comment #14
lendudeSince the breadcrumb is probably build up from the titles, this might be overlapping with #3076748: In D8 Search page titles are not rendered from the provided label value wherein D7 it is working fine, didn't dig too deep.
Comment #19
quietone commentedThe Search Module was approved for removal in #3476883: [Policy, no patch] Move Search module to contrib .
This is Postponed. The status is set according to two policies. The Remove a core extension and move it to a contributed project and the Extensions approved for removal policies.
The deprecation work is in #3565780: [meta] Tasks to deprecate the Search module and the removal work in #3565783: [meta] Tasks to remove the Search module.
Search will be moved to a contributed project before Drupal 12.0.0 is released.