Problem/Motivation
Track the steps needed to deprecate extension Search. See Remove a core extension and move it to a contributed project of the deprecation policy.
The removal of extension Search was approved in #3476883: [Policy, no patch] Move Search module to contrib.
Remaining tasks
- Begin finding someone to maintain the contrib version of the extension.
Add the extension to the list of the Upcoming Deprecations.- Move integrations implemented by other modules to the extension.
Create child issues or child meta issues, as needed, to address the following points. Not all points will apply to all extensions.- Move non-migration tests to the extension.
- Move Help Topics to the extension.#3565822: Move mention of Search from core help to search module
- Move HelpSearch plugin #3581109: Move HelpSearch to Search sub-module
- Move search from User to Search #3588379: Move search from user module to Search
- Move search from Node to Search #3587564: Move search functionality from node to Search module
- Handle use of search in olivero_test #3586616: Remove search from olivero_test module
- Remove the extension from one or more profiles #3567672: Remove Search module from Standard, Umami and recipes
- Standard
- Umami
- nightwatch_a11y_testing #3584694: Remove Search module from nightwatch_a11y_testing profile & tests
- Remove references to the extension from database dumps.
- Remove templates from the extension’s markup.
- Remove templates from themes that are staying in core, leave them in deprecated themes
- Keep skipping the template in the stable copies test.
- Do a thorough search of core for any remaining references to the extension. If references are found, outside of the extension, then create issues to remove the references.
- Create the contrib project with a stable release, before the alpha version of the major release. Follow the process in Create the contrib project with a stable release for creating the sub tree split.
- Deprecate the core extension. #3565781: Deprecate the Search module
- Open an issue, 'Ensure that Search module does not get special core treatment' in the packages.drupal.org issue queue to ensure that the composer namespace for the contributed project matches the core one after removal. This is to allocate the
drupal/searchComposer namespace to contrib extension rather than the core extension. - Update the Deprecated and obsolete extensions
Comments
Comment #2
quietone commentedComment #3
quietone commentedComment #4
quietone commentedThese tests install Search
Comment #5
quietone commentedTalked to catch about about skipping handling the migration tests due to the fact the Migrate Drupal and family is being removed and not ported to contrib and that the migrations in Search are all configuration migrations. We both agreed that it OK in this case. I have updated the issue summary accordingly.
Comment #6
quietone commentedComment #7
quietone commentedComment #9
quietone commentedComment #10
smustgrave commentedJust noting that there is some config in the node module for search.
Comment #11
quietone commentedYes, search is in lots of places. Support for search is in: claro, default_admin, demo_umami, starterkit, and olivero. Also theme.api.php and entity.api.php. And comment module.
Comment #12
quietone commented#3575605: Move tests of search to search module committed
Comment #13
quietone commentedI think these are the config that need to be handled.
Comment #14
kentr commentedOlivero has some libraries related to Search.
Comment #15
quietone commentedComment #16
quietone commentedComment #17
quietone commentedComment #18
quietone commentedComment #19
quietone commentedComment #20
quietone commentedComment #21
quietone commentedComment #22
quietone commentedComment #23
quietone commentedSearch core for usages of the Search module is difficult because 'search' is also used in database code and view for example.
For themes alone there are 321 uses of the word search.