TYPO3 Core

The problem:¶

When using the Live Search in the TYPO3 backend, most users want to directly edit a record. However, the current behavior always triggers the first available action, which for pages and database records is typically open_page_details. This opens the List module at the location where the record is stored. In many cases, this is not the most efficient action—especially when the record is not immediately visible due to pagination, filtering, or workspace restrictions. Users are then forced to manually locate the record, adding unnecessary steps to a simple task.

Current behavior:¶

Clicking a search result always executes the first defined action. For pages and records, this is open_page_details. Users who frequently edit records must take extra steps to get to the editing interface.

Proposed solution:¶

Introduce a new User TSconfig setting that allows users to define their preferred default action for search results. If no setting is defined, the system will continue to use the first action as before—ensuring full backward compatibility.

Configurable actions:¶

For pages:¶

• edit_record (added and new default)
• open_page_details
• preview_page

For database records:¶

• edit_record (new default)
• open_page_details

Examples¶

• options.liveSearch.defaultAction.pageRecords = edit_record
• options.liveSearch.defaultAction.databaseRecords = open_page_details