Project

General

Profile

Actions

Feature #21201

closed

use navigation title if available

Added by Michael Stopp about 15 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2009-10-07
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

The path displayed in the search hits can become quite chaotic if people use very long page titles in combination with navigation titles. It would be better if the navigation title was used (if available). Thus the path would better reflect the website structure as the user experiences it in the navigation or on a sitemap.
The section selector on the advanced search form suffers from the same problem.

In a perfect world there should be a TS option that allows you to set whether the navigation title should be taken into account or not.
(issue imported from #M12143)

Actions #1

Updated by Nils Hodyas over 14 years ago

I'll second that request.
It would also be cool in cases where a menu is build from subpages of a sysfolder.

Actions #2

Updated by over 14 years ago

I think this request is too specific. IMO it would be nice to make the indexed_search title output configurable by Typoscript so you can choose which field of the pages DB record is taken.

Then you could also use stdWrap to manipulate the output, i.e. we need to stripHtml the title output as we are using <br /> in titles.

Actions #3

Updated by Michael Stopp over 14 years ago

Just to clarify on the previous note: in my original request I was NOT referring to the title (###TITLE### marker) of a search hit, but only to the path (###PATH### marker)! (I admit that the item summary is not very clear in that respect.)
The path can be seen as the equivalent to a breadcrumb navigation and I don't see many scenarios where somebody has navigation titles but wouldn't want them to be used in a breadcrumb context (though I'm sure other people will disagree ;-).

Actions #4

Updated by Alexander Opitz over 11 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)?

Actions #5

Updated by Alexander Opitz about 11 years ago

  • Status changed from Needs Feedback to Closed

No feedback for over 90 days.

Actions

Also available in: Atom PDF