Project

General

Profile

Actions

Bug #68393

closed

Link in fluidtemplate to root-page is ignored

Added by Muriel le Pair almost 9 years ago. Updated almost 8 years ago.

Status:
Closed
Priority:
-- undefined --
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2015-07-20
Due date:
% Done:

0%

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

Description

Hi,

This used to work fine up to version 6.2.13 but in TYPO3 6.2.14 a link in the fluidtemplate to the rootpage is ignored.

So this (if 1 is the rootpage):
<f:link.page pageUid="1">homepage</f:link.page>

should render:
<a href"/">homepage</a>

instead it displays:
homepage

When I link to any other page but the rootpage it works fine:
<f:link.page pageUid="2">page 2</f:link.page>

renders:
<a href"/page-2">page 2</a>

--
kind regards,

Muriel le Pair

Actions #1

Updated by Riccardo De Contardi almost 9 years ago

@Muriel It seems a bit strange, because after a quick test on my existing installation, it works fine;

just some stupid questions:

1) are you sure your homepage has ID=1?
2) is the page hidden?
3) do you use realurl? (I guess so...) what if you try to disable it?

Actions #2

Updated by Muriel le Pair almost 9 years ago

@Riccardo to answer your questions:

1) Yes :)
2) No, but the homepage is set to display the content of the page called home (id=2)
3) It does work if I disable realurl. Mmmm.. does this mean it's a bug in Realurl?

Actions #3

Updated by Muriel le Pair almost 9 years ago

It works in TYPO3 6.2.13 with realurl 1.13.3,
if doesn't work in TYPO3 6.2.14 with realurl 1.13.3

Actions #4

Updated by Riccardo De Contardi almost 9 years ago

@Muriel so.... ID=1 is a shortcut to the page with ID=2? I don't know how Realurl behaves on this scenario... it could be a misconfiguration and not a bug;
If you agree, I would close this and ask you to seek for help on Slack (https://forger.typo3.org/slack) or mailing lists, as these are the proper places to get help.

Actions #5

Updated by Muriel le Pair almost 9 years ago

"ID=1 is a shortcut to the page with ID=2?"
No id=1 displays the content of id=2.

I still consider this to be a bug, since it works fine in TYPO3 6.2.13 and it doesn't work in TYPO3 6.2.14, it makes sence to me that it is a bug in the latest version of TYPO3 and not in realurl.

Actions #6

Updated by Riccardo De Contardi almost 9 years ago

  • Status changed from New to Needs Feedback

Ah, ok...my first attempt to reproduce it failed :S
can you post your realurl configuration?

Thank you

Actions #7

Updated by Michael Ganner almost 9 years ago

Same problem here. realurl 1.13.3 and T3 6.2.14.

I tried

<v:link.typolink configuration="{parameter: '{reference.link}', ATagParams: 'class=\"slider-full-link\"'}"><!-- --></v:link.typolink>

as well as
<f:link.page class="slider-full-link" pageUid="{reference.link}" title="{reference.alternative}"></f:link.page>

If the link points to a rootpage the href-attribute is empty.

Turning off realurl solves the problem but is not really a solution for a productive environment.

Actions #9

Updated by Riccardo De Contardi almost 9 years ago

  • Assignee set to Muriel le Pair

Muriel, does the suggestion from Michael Ganner help you?

Actions #10

Updated by Muriel le Pair almost 9 years ago

No,

config.typolinkCheckRootline = 1 had already been set.

Actions #11

Updated by Riccardo De Contardi over 8 years ago

  • Assignee deleted (Muriel le Pair)
Actions #12

Updated by Alexander Opitz over 8 years ago

  • Status changed from Needs Feedback to New
  • Target version changed from 6.2.15 to 6.2.16
  • Is Regression changed from No to Yes
Actions #13

Updated by Claus Due over 8 years ago

I suspect this is RealUrl manipulating the generated URL. I am not personally aware of any configuration options, in PHP or TS, that would affect this - but it seems rather obvious that RealUrl is the cause. I suggest reporting this issue to RealUrl's tracker (but to make matters worse, I'm not sure which one is the official sucessor, because github has a few versions of the extension at this point...)

But in any case this doesn't seem related to the TYPO3 core. And Fluid itself isn't doing anything to the pageUid (only if you don't provide it, which of course you do).

I recommend closing this issue.

Actions #14

Updated by Claus Due over 8 years ago

  • Category changed from Fluid to Frontend
  • Status changed from New to Needs Feedback
  • Priority changed from Must have to -- undefined --
  • Target version deleted (6.2.16)

I have:

  • Moved this to "Frontend" since it's a general problem not isolated to Fluid's ViewHelpers. I did this rather than move it to the EXT:realurl bug tracker because that one no longer gets monitored and the issue would get no official response there.
  • Removed the "target version" since it's unlikely this needs to be patched in the core.
  • Set priority to "undefined" for the same reason.
  • Set status to "needs feedback" because a decision is required (see my last comment).

If any team member agrees please close this issue and/or refer it to whichever support channel is still open for EXT:realurl.

Actions #15

Updated by Alexander Opitz about 8 years ago

  • Is Regression changed from Yes to No

Hi Muriel le Pair,

does this issue is fixed by updating to a newer version of RealURL?

Actions #16

Updated by Riccardo De Contardi almost 8 years ago

  • Status changed from Needs Feedback to Closed

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.

Thank you

Actions

Also available in: Atom PDF