Bug #77566
closedLivesearch doesn't submit after first empty result
100%
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 optionpreventBadQueries: 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.
Updated by Gerrit Code Review over 8 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/49532
Updated by Gerrit Code Review about 8 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/49532
Updated by Alexander Jahn about 8 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 99c79e5c3e62315c0538c211d5f2ec9fb1432a56.
Updated by Gerrit Code Review about 8 years ago
- Status changed from Resolved to Under Review
Patch set 1 for branch TYPO3_7-6 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/49562
Updated by Alexander Jahn about 8 years ago
- Status changed from Under Review to Resolved
Applied in changeset 3c929dae0b9525b0503d52c65810a13ced72f5df.