Bug #21976
closed
missing page-link-address in menu
Added by Kurt Kunig almost 15 years ago.
Updated almost 11 years ago.
Description
If you put a clear numeric alias into the alias-field of a page, e.g. "2010", the menu-item in the frontend for this page links to the root and not to the mentioned page!?
If you add only one alphabetic character at the beginning or at the end of the alias, e.g. "y2010" or "2010y", the menu-link will be correct!
create a page, better a subpage and give'm a numeric alias.
(issue imported from #M13267)
- Status changed from New to Needs Feedback
- Target version deleted (
0)
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
Alexander Opitz wrote:
The issue is very old, does this issue exists in newer versions of TYPO3 CMS (4.5 or 6.1)?
Yes! Still in 4.7.x and also in 6.1!
Pure numeric alias (1234): no link to the page
Numeric alias with an underscore at the beginning (_1234): the link will be "1234.html" (numeric without the underscore!?)
Btw, why you use numeric aliases? They may collide with the uid of a page (I think). as you write "1234.html" Do you use simulatestatic, RealURL or cooluri?
Alexander Opitz wrote:
Btw, why you use numeric aliases? They may collide with the uid of a page (I think). as you write "1234.html" Do you use simulatestatic, RealURL or cooluri?
Why!? - I forgot that but I found the failure out. Nevertheless, it's not correct. Sitenames like 12345.html are allowed generally - or not!?
FYI I use realUrl.
Long time ago I used simulatestatic and IMHO it produced Sitenames like
home.1234.html
and while finding the uid it took the number before the last point so home.1234.html and 1234.html was the same (out of the view of simulatestatic).
But maybe I don't remember it wrong.
It seams that this problem can't be changed. So I would like to close this issue and we should add a check for valid aliases: #21156
Would this be ok for you?
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this ticket.
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.
Also available in: Atom
PDF
Updated by 
Updated by