Project

General

Profile

Actions

Bug #55118

closed

sysext:documentation - search shows weird behaviour

Added by Michael Schams almost 11 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Documentation
Target version:
Start date:
2014-01-18
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.4
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

The search for docs in sysext:documentation shows a weird, unexpected behaviour in TYPO3 CMS 6.2 LTS beta4

Fresh, clean TYPO3 CMS 6.2 LTS beta4 installation.
Go to Backend -> HELP -> Documentation
Switch from function "Show Documentation" to "Download Documentation" (dropdown box at the top)

Example 1: Security Guide
The "Security Guide" appears in the list (key: t3security)
Enter "security" -> No matching records found
Enter "sec" -> No matching records found
Enter "se" -> No matching records found

Example 2: something with "typo3"
Several docs with the keyword "TYPO3" appear in the list
Enter "typo3" -> No matching records found
Clear the search input field (complete list appears as expected)
Enter "typo3" and remove the "3" (backspace) -> result list looks ok

Back to example 1:
Enter "security" and remove the last character "y" (backspace) -> record appears correctly

Example 3: ext:rsaauth
The manual I am looking for is "RSA authentication for TYPO3" (ext:rsaauth)
Enter "rsa" -> No matching records found
Enter "rsa" plus a space at the end, remove the space (backspace) -> looks ok
Clear the search input field
Enter "rsa" -> now it looks ok (was not before, see above)
Clear "page content cache" (flash-icon at the top)
Enter "rsa" again -> No matching records found

Example 4: RTE
Enter "rte" -> two docs appear in list: t3api and t3tsref
Remove the last character "e" from "rte" -> two different docs appear: rtehtmlarea and t3start
Add the "e" again -> No matching records found


Files

screenshot0006.png (29.9 KB) screenshot0006.png Michael Schams, 2014-01-18 11:16
screenshot0007.png (224 KB) screenshot0007.png Michael Schams, 2014-01-20 10:34
screenshot0008.png (64.3 KB) screenshot0008.png Michael Schams, 2014-01-20 10:38
Actions #1

Updated by Michael Schams almost 11 years ago

Uh! Just realised: I get a JavaScript error on every key stroke when entering the search term.
See attached screenshot.

Actions #2

Updated by Xavier Perseguers almost 11 years ago

  • Status changed from New to Accepted

In fact

Actions #3

Updated by Xavier Perseguers almost 11 years ago

  • Target version set to 6.2.0

Problem seems to be related to the bStateSave, when I comment out this feature (e.g., in our case for the "download" action), then filtering is just working as expected.

Actions #4

Updated by Xavier Perseguers almost 11 years ago

Michael Schams wrote:

Uh! Just realised: I get a JavaScript error on every key stroke when entering the search term.
See attached screenshot.

I cannot reproduce your error. This is related to missing jquery in your example. Can you share if you have special settings?

Actions #5

Updated by Michael Schams almost 11 years ago

Xavier Perseguers wrote:

I cannot reproduce your error. This is related to missing jquery in your example. Can you share if you have special settings?

It's a brand new, empty, fresh TYPO3 6.2.0beta4 installation. No pages, no configuration no special settings, no update or so.

  • extract typo3_src-6.2.0beta4.tar.gz in DocumentRoot
  • access Install Tool
  • go through Installation Wizard
  • login at TYPO3 backend
  • open FireBug (if you are using Firefox)
  • go to: HELP > Documentation [JavaScript error appears]
  • enter a character in search input field [on each key stroke: JavaScript error appears]

jQuery seems to be included correctly and before the (merged) JavaScript file that causes this error.
See attached screenshot0007.png. File jquery-1.9.1.min.js exists and is successfully included in the page (content frame).
Inclusion of file "merged-78caa19ab980b65dfa87a5aa4f6f5601-e5addec580c9020fab1cf83b45c5fb6c.js" follows further down.

Actions #6

Updated by Michael Schams almost 11 years ago

Third screenshot0008.png shows the line in file "merged-78caa1 ... 5fb6c.js", that causes this error.
Not sure, if this helps anyone :-)

Actions #7

Updated by Mathias Schreiber almost 10 years ago

  • Status changed from Accepted to Resolved

works on master

Actions #8

Updated by Riccardo De Contardi about 7 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF