Project

General

Profile

Actions

Bug #55903

closed

Constants are not resolved in backend layout config field

Added by aromedia no-lastname-given almost 11 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
Backend User Interface
Target version:
-
Start date:
2014-02-12
Due date:
% Done:

0%

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

Description

Since in backend layout config field there's a TypoScript-like syntax i would expect to use constants as well.

For example:
backend_layout {
colCount = 3
rowCount = 2
rows {
1 {
columns {
1 {
name = Navigation links
colPos = {$colPos.colNav}
}
2 {
name = Content
colPos = {$colPos.colContent}
The constants were resolved except of the backend layout config field. It would be easier for configuration.

Actions #1

Updated by Georg Ringer almost 11 years ago

  • Priority changed from Must have to Could have
Actions #2

Updated by Mathias Schreiber almost 10 years ago

  • Status changed from New to Needs Feedback
  • Assignee set to Mathias Schreiber

Which constants are you refering to?
Do you imagine a new field in the BE layout or do you want to re-use the constants from a typoscript template?

Actions #3

Updated by Riccardo De Contardi over 9 years ago

he refers to re-using some constants from a typoscript template; But I think this should be moved to Features...

Actions #4

Updated by Alexander Opitz over 9 years ago

  • Status changed from Needs Feedback to Closed
  • Assignee deleted (Mathias Schreiber)

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