Project

General

Profile

Actions

Bug #77566

closed

Livesearch doesn't submit after first empty result

Added by Alexander Jahn over 8 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2016-08-22
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
7
PHP Version:
7.0
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Once livesearch can't find results for a search string, following searches are not executed.
This is the default behaviour of jQuery autocomplete. The option
preventBadQueries: false
can be used to fix the issue.

Example 1:
An editor wants to find tt_content with UID 12345 entering '#content:12345'.
The record exists and is accessible.

The search fires once '#co' is entered but does not find anything. Subsequent characters are not send to the Server.

Entering '#content:12345' via copy&paste as a complete string works.

Example 2:
An admin wants to find the same record by searching for the UID only.

Entering '123' might find some record containing the string '123' in bodytext.
Entering '1234' finds nothing.
Entering '12345' does not execute the search.
Copy&pasting the whole string works.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #78457: Suggest-wizard does not submit after first empty resultClosed2016-10-27

Actions
Actions

Also available in: Atom PDF