Project

General

Profile

Actions

Bug #21156

closed

Number as page-alias shouldn't be allowed

Added by Tobias Schaefer over 14 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Backend User Interface
Target version:
Start date:
2009-09-30
Due date:
% Done:

0%

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

Description

It's possible to set a number as an alias of a page. This conflicts with the page-id. TYPO3 should correct the alias by adding a string or deny saving the page-properties.

(issue imported from #M12084)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #21976: missing page-link-address in menuClosed2010-01-17

Actions
Actions #1

Updated by Oliver Hader over 14 years ago

A new evaluation/validation method should be introduced:
"NaN" or "noint"

Actions #2

Updated by Alexander Opitz over 10 years ago

  • Target version deleted (0)
  • Is Regression set to No

Why shouldn't numbers not allowed as page alias?
Beside that there seams to be an issue with them in #21976

Actions #3

Updated by Tobias Schaefer over 10 years ago

  • Target version set to 6.2.0

Of course TYPO3 should allow numbers in the alias field in general. It should only deny entering numbers only (with no other characters). TYPO3 misinterpret the alias eg. "123" as id and delivers the page with the id "123" instead of the page with the alias "123". If there is no page with an id "123" an error message is returned saying the requested page doesn't exist (which is correct).

Actions #4

Updated by Alexander Opitz over 10 years ago

So this makes only sense if you don't use RealUrl or something like that?

Actions #5

Updated by Tobias Schaefer over 10 years ago

Yes, the problem should only occur if you use: index.php?id=[numbers only alias]

Actions #6

Updated by Alexander Opitz over 10 years ago

It seams there are also some functions that try to validate a internal link with that alias. See #21976, so we should avoid such aliases.

Actions #7

Updated by Mathias Schreiber over 9 years ago

  • Category set to Backend User Interface
  • Target version changed from 6.2.0 to 7.4 (Backend)
Actions #8

Updated by Susanne Moog over 8 years ago

  • Target version changed from 7.4 (Backend) to 7.5
Actions #9

Updated by Benni Mack over 8 years ago

  • Target version changed from 7.5 to 7 LTS
Actions #10

Updated by Gerrit Code Review over 8 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/44113

Actions #11

Updated by Gerrit Code Review over 8 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/44113

Actions #12

Updated by Frank Nägler about 8 years ago

  • Status changed from Under Review to New
Actions #13

Updated by Benni Mack over 5 years ago

  • Status changed from New to Rejected

Hey Tobias,

this feature has been superseded by the new Page-based URL slug handling. The field pages.alias had various drawbacks and will be removed in TYPO3 v10.0. If you still experience issues with the new handling, please open up a new ticket.

Thanks.
Benni.

Actions

Also available in: Atom PDF