TYPO3 Core

To circumvent this you can use just a plain "a" tag as the menu link has not to be processed via a view helper.

Maybe the f:link.typolink should even throw a warning (deprecation log?) when parameter is starting with a slash?

"Don't put rendered pre-rendered stuff where it doesn't belong" ;-)

Philipp Kitzberger wrote in #note-3:

Maybe the f:link.typolink should even throw a warning (deprecation log?) when parameter is starting with a slash?

People actually use it like this as well "/fileadmin/myfile.zip", how should we handle this then?

Georg Ringer wrote in #note-5:

hey Peter,

I am closing this issue. using just / in the f:link.typolink viewhelper should really not be something you would do. either use <f:link.page or just use a regular a-tag if you know already the url

I'm not really happy with just closing it, as it's still a bug. It works with /foo but does not work with / - so in my opinion, this is not acceptable behavior.

I think it should either throw an exception because it's not allowed, or the behavior should be consistent. Throwing an exception is, of course, not feasible, so in my opinion, the only way to solve the problem is to fix it.

It is not always obvious that typolink is called twice - at least not if you use third-party code such as fluid_components. Of course, it is unfavorable if typolink is called twice, but as I said, the behavior should still be consistent and not just happen in the event that only a / is passed.