Project

General

Profile

Actions

Bug #25267

closed

pages.layout.altLabels won't accept values beginning with numbers - error 403!

Added by Lukas Musilek over 13 years ago. Updated about 10 years ago.

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

0%

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

Description

after updating from 4.2. to 4.5.2. i have the following strange behaviour:

TCEFORM.pages.layout.altLabels only works with values, where the first character istn a number!

works:
TCEFORM.pages.layout.altLabels.1 = Spalte

doenst work:
TCEFORM.pages.layout.altLabels.1 = 1 Spalte
in this case, i get a 403 error, and the hole system seems to be down for about 20-30 seconds. (no ping, network times out, ...).

no relevant entries in typo3-log, or apache log.
file and folder permissions should be ok (files 644, folders 755)

(issue imported from #M17879)

Actions #1

Updated by Alexander Opitz over 10 years ago

  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.3)?

Actions #2

Updated by Riccardo De Contardi about 10 years ago

Tested with TYPO3 6.2.6

I've not understood if the problem had been encountered on frontend or backend ("TCEFORM.pages.layout.altLabels.1 = 1 Spalte" is TS Config, so it should affect only BE, shouldn't it?).

I added TCEFORM.pages.layout.altLabels.1 = 1 Spalte to page TS Config and selected it for a page, but I did not see strange behaviours, both backend and frontend still works as usual (I cleared cache, refreshed the page...)

Actions #3

Updated by Alexander Opitz about 10 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days from author and with the given writing from Riccardo De Contardi I will 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