Bug #20378

Problem with sorting categories

Added by Tobias Schweizer over 10 years ago. Updated almost 4 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Indexed Search
Target version:
-
Start date:
2009-04-29
Due date:
% Done:

0%

TYPO3 Version:
4.3
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

indexed_search (extended mode) always uses the category "date of last change" as a sorting criterion even though the user selects another category as a sorting criterion. When the user selects a category and submits his request, his selection of category does not remain active. Indexed_search switches back to the category "date of last change".

We use indexed_search version 2.11.1
(issue imported from #M11011)

History

#1 Updated by Alexander Opitz over 6 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • TYPO3 Version set to 4.3

The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?

#2 Updated by Tizian Schmidlin over 6 years ago

This is still an issue but since I think we figured out, why this happens: the sorting changes automatically to m_time in order to save performance when looking up multiple search words, thus the sorting category is reset.

It would be nice to have at least an option for indexed search in order to disable this specific behaviour, even though search then take longer to proceed.

#3 Updated by Alexander Opitz over 6 years ago

  • Status changed from Needs Feedback to New

#4 Updated by Mathias Schreiber almost 5 years ago

  • Target version set to 7.5
  • Is Regression set to No

#5 Updated by Benni Mack about 4 years ago

  • Target version changed from 7.5 to 7 LTS

#6 Updated by Mathias Schreiber almost 4 years ago

  • Target version deleted (7 LTS)

#7 Updated by Tizian Schmidlin almost 4 years ago

I'd just like to say, that this is still an issue (but we have a workaround for it, so no biggy).

If there is anything to be done with the search and it is completely replaced by something else, IMHO you can close the issue.

Regards
Tizian

Also available in: Atom PDF