Problem/Motivation

The Search pages page contains four sections that relate to the configuration of Search and Indexing (Indexing progress, Indexing throttle, Default indexing settings, and Logging) and one section that contains a list of Search pages with the option to add new such pages.

This is a non-standard set-up because on similar pages for other modules such configuration and list are two separate pages, usually connected to each other as tabs. On these list pages the primary button "Add foo" is located at the top of the page.

This is a usability issues because users will not expect such a list at the bottom of a configuration page, and therefore are likely to overlook that it's possible to add more custom search pages. It also makes it more possible to grant user access to add more search pages, without granting them the permission to change the indexing configuration.

Proposed resolution

Split the content of the "Search pages" page on into "Search pages" and "Indexing", or "Indexing configuration" or so.

Remaining tasks

User interface changes

This is a UI change and the hook_help text will need to be edited accordingly.

API changes

Data model changes

Comments

ifrik created an issue. See original summary.

haza’s picture

Issue summary: View changes
Status: Active » Needs review
StatusFileSize
new33.24 KB
new25.71 KB
new16.05 KB

Here is a first patch that splits this into 2 pages.

I did not touch anything in tests right now, and hook_help still needs to be updated.

haza’s picture

Also, if #2752915: Rename "Add page" to "Add search page" went in, we'll need to reroll this patch.

ifrik’s picture

Thanks Haza,
that works as I envisioned it. We will need some review by the module maintainer for this as well.

Status: Needs review » Needs work

The last submitted patch, 2: split_search_page_in_a-2752927-2.patch, failed testing.

haza’s picture

Status: Needs work » Needs review
StatusFileSize
new21.09 KB
new5.21 KB

Working on updating the tests. This should have less failling tests.

ifrik’s picture

Issue tags: +Needs usability review
yoroy’s picture

Status: Needs review » Needs work
Issue tags: -Needs usability review

The general idea proposed here makes a lot of sense. Nice find, it's indeed a non-standard setup to have this list of pages at the bottom of a settings page.

- I think with the pages list on a seperate page we can also remove the collapsible fieldset around it.
- The 'Add new page' button needs to get the button--primary class to make it blue
- The current standard page titles for these kinds of pages are "List" and "Settings" (See: forums, books, feed aggregator). I think it should definately say "List", but for example "admin/config/regional/language" uses "Detection and selection" as the label for the second "Settings" tab. I don't think we should use the "Configuration" word here. Maybe "Indexing" or "Index settings"?
- A different issue most likely, but what is that "Search page type" dropdown even supposed to be doing? I don't see it have any effect when I make a selection

Thanks for working on this!

ifrik’s picture

Thanks yoroy,

there also is a separate issue for just the button, because it looked like an quick novice issue: #2752915: Rename "Add page" to "Add search page".
There the proposal to turn the button into a primary button was rejected.

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.

ifrik’s picture

Issue tags: +Dublin2016

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: Needs work » 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!

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.

quietone’s picture

Status: Postponed (maintainer needs more info) » Postponed

The 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.