Project

General

Profile

Actions

Bug #60980

closed

missing an easy way to use translations in a menu.speacial = browse

Added by Dieter Porth over 9 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2014-08-14
Due date:
% Done:

0%

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

Description

I want to build a easy pagination for my site with text like "next page" or "revious page". I define the following translation for this

LLL:fileadmin/Resources/Private/Language/RootMenu.xlf:menu.pagination.next = next

and I define in a contant file the translation reference:

root.menu.pagination.next = {LLL:fileadmin/Resources/Private/Language/RootMenu.xlf:menu.pagination.next}

I used the constants in TypoScript in two way
@
lib.menu.pagination.main = HMENU
lib.menu.pagination.main {
special=browse
special {
items = next
#shown result => "{LLL:fileadmin/Resources/Private/Language/RootMenu.xlf:menu.pagination.next}"
prev.fields.title = {$root.menu.pagination.next}
}
1 = TMENU
1 {
NO = 1
NO.allWrap = |
}
}

#shown result => "abc"
lib.text = TEXT
lib.text.value = {$root.menu.pagination.next}
lib.text.insertData = 1
@

It would be fine, if the constant would work in both situation in the same way.

I know that 'lib.text.value' and 'prev.fields.title' have different datatypes.

Why can I write something like the following?

prev.fields.title = {LLL:fileadmin/Resources/Private/Language/RootMenu.xlf:menu.pagination.next}
prev.fields.title = LLL:fileadmin/Resources/Private/Language/RootMenu.xlf:menu.pagination.next

I want to use easyly and directly my translation file for the 'title'-Information.

Dieter

Actions #1

Updated by Steffen Müller over 9 years ago

  • Tracker changed from Suggestion to Bug
  • Project changed from 1865 to TYPO3 Core

Moved to core issue tracker.

Actions #2

Updated by Daniel Goerz almost 8 years ago

  • Status changed from New to Needs Feedback
  • Is Regression set to No

This bug report is very old. Does this bug still occur in TYPO3 7 LTS and/or the master? And if so how can it be reproduced?

Actions #3

Updated by Alexander Opitz over 7 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF