Project

General

Profile

Actions

Bug #51960

closed

Fluid ViewHelper f:link.page fails with link to start page

Added by Norbert Stooss about 11 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2013-09-12
Due date:
% Done:

0%

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

Description

After Update TYPO3 6.1.3 to TYPO3 6.1.4 and TYPO3 6.1.5

<f:link.page pageUid="1"><f:cObject typoscriptObjectPath="lib.topAnschriften"></f:cObject></f:link.page>

doesn't build a link.

Norbert


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #64319: FLUID: "f:link.page" and RealURLClosed2015-01-16

Actions
Has duplicate TYPO3 Core - Bug #52128: Fluid ViewHelper f:link.page fails at home link.Closed2013-09-19

Actions
Actions #1

Updated by Markus Klein about 11 years ago

Hi Norbert!

What else is happening? Does it show the content created by lib.topAnschriften?
Is pid 1 accessible?

Actions #2

Updated by Norbert Stooss about 11 years ago

Hi Markus,

I have build a RECORDS

  1. topAnschriften
    lib.topAnschriften = RECORDS
    lib.topAnschriften.wrap = <div id="topAnschriften">|</div>
    lib.topAnschriften.source = 1
    lib.topAnschriften.tables = tt_content

and integrate to page 1.
Look at http://haus.hausundgrund-oehringen.de/

Norbert

Actions #3

Updated by Markus Klein about 11 years ago

Looks like you're running into this issue: #50751

Actions #4

Updated by Anja Leichsenring about 11 years ago

Hi Norbert,

that happens if you point to a page that is not available (hidden, restricted). So you need to point to a page that is accessible to generate a link. No bug here, this is how typolink works since ever.

Greetz Anja

Actions #5

Updated by Anja Leichsenring about 11 years ago

  • Status changed from New to Rejected
Actions #6

Updated by Norbert Stooss about 11 years ago

Hi Anja,
I don`t understand your answer. Die Page 1 is the Homepage and not hidden or anything.
It`s the first page and you see also "the logo with text" to this is the link.

The link is going until TYPO3 6.1.3. With the update to 6.1.4 the link is broken.

Norbert

Actions #7

Updated by Wouter Wolters about 11 years ago

Hi Norbert,

Can you try to debug in the PageViewHelper what the $uri variable is?
And what is the HTML this code will provide in previous releases?

Greetz Wouter

Actions #8

Updated by Norbert Stooss about 11 years ago

Hi Wouter,

I cannot access this file, because it's a symlink to 6.1.5

/typo3/sysext/fluid/Classes/ViewHelpers/Link/PageViewHelper.php

The following call gives ZERO back
<f:debug title="title">{f:link.page(pageUid: 1)}</f:debug>

The following call gives an empty string back
<f:debug title="title">{f:uri.page(pageUid: 10)}</f:debug>

Norbert

Actions #9

Updated by Norbert Stooss about 11 years ago

I have noticed that the link gets active only on the side on which the object (text with picture) is tied directly. Since TYPO3 6.1.4 it isn't recognized by the link that the object is tied by RECORDS on the page 1.

Norbert

Actions #10

Updated by Markus Klein about 11 years ago

  • Subject changed from Update TYPO3 6.1.3 to TYPO3 6.1.4 and TYPO3 6.1.5 to Fluid ViewHelper f:link.page fails with link to start page
  • Status changed from Rejected to New

Norbert, I didn't understand you last two posts. Can you please explain again?

Actions #11

Updated by Markus Klein about 11 years ago

  • Is Regression changed from No to Yes
Actions #12

Updated by Helmut Hummel about 11 years ago

Anja Leichsenring wrote:

that happens if you point to a page that is not available (hidden, restricted). So you need to point to a page that is accessible to generate a link. No bug here, this is how typolink works since ever.

If you use realurl, the link to the homepage (root page) might be empty, if you use baseURL and not absRefPrefix. typolink will work correctly in this case, the changed page link view helper obviously not.

@Norbert: A workaround is to set

config.absRefPrefix = /

Actions #13

Updated by Norbert Stooss about 11 years ago

Ok perfect. It works

Norbert

Actions #14

Updated by Anja Leichsenring about 11 years ago

Hello @all review,

I investigated this issue and I am not able to reproduce.

My config:
current master
realurl patched for master
config.baseURL set
config.absRefPrefix not set

I use a <f:link.page pageUid="1">Home</f:link.page>.
As long as the page with uid 1 is accessible (and it is my Startpage), the link is generated as
<a href="/">Home</a>
When I disable the page, the link is not shown. So whatever the issue might be, I am not able to reproduce. Sorry.

Actions #15

Updated by Anja Leichsenring about 11 years ago

  • Status changed from New to Needs Feedback
Actions #16

Updated by Marc Bastian Heinrichs about 11 years ago

Could also be a realurl thing.
Norbert, what is your config of [init][emptyUrlReturnValue]?

Actions #17

Updated by Anja Leichsenring almost 11 years ago

  • Status changed from Needs Feedback to Closed

No feedback since four month. Feel free to reopen, if issue persists.

Actions #18

Updated by Ghanshyam B. Gohel over 9 years ago

Hola,

I have similar issue.

<f:link.page pageUid="2" class="navbar-brand navbar-brand-image">Startseite</f:link.page>

But link not created. When I disable realurl it's work. Also I need pretty urls, so I have found somewhere else "emptyUrlReturnValue" and set in typo3conf/realurl_conf.php

Full code:
'init' => array (
'enableCHashCache' => '1',
'appendMissingSlash' => 'ifNotFile',
'enableUrlDecodeCache' => '1',
'enableUrlEncodeCache' => '1',
'emptyUrlReturnValue' => '/',
),

Actions #19

Updated by Patrick Crausaz about 9 years ago

I got the same problem.
Link is working just fine when I disable realUrl.

Workaround "config.absRefPrefix = /" works in my case.

Here is another related issue: #64319

Actions #20

Updated by Kaan Sanli about 8 years ago

  • Assignee set to Anja Leichsenring
  • TYPO3 Version changed from 6.1 to 6.2
  • Is Regression changed from Yes to No

I had the same behaviour, that a link to page with uid = 1 was not rendered, using T3 6.2.26, tx_news 3.2.5 and realurl 1.13.6.

It doesn't matter if the linked page has uid 1 or 2 or whatever. The trigger for the behaviour lies in using the start page as site root. Having set is_siteroot = 1, the link is not rendered. Having set is_siteroot = 0, the link is rendered.

And yes, it is a realurl thing. By deactivating realurl or setting config.absRefPrefix = / (although I'm using baseURL here) on news single view page, the behaviour of is_siteroot is completely ignored and the link to the rootpage works.

The workaround emptyUrlReturnValue = '/' in init-array of my realurlconf - stated by Ghanshyam B. Gohel - works fine for me, i will use this from now on.
Nonetheless, there is an influence of realurl on fluid ViewHelper f:link.page, when linking to rootpage with setting is_siteroot = 1.

Reopen up this ticket?

Actions #21

Updated by Markus Klein about 8 years ago

  • Status changed from Closed to New
  • Assignee deleted (Anja Leichsenring)
  • TYPO3 Version changed from 6.2 to 6.1
Actions #22

Updated by Benni Mack over 7 years ago

Sounds more like a realurl issue to me.

Actions #23

Updated by Riccardo De Contardi about 7 years ago

  • Status changed from New to Closed

Based on comments 19 and 20, I close this for now as it should be realurl-related. Please open an issue here: https://github.com/dmitryd/typo3-realurl/issues

If you think that this is the wrong decision or have more information about how to reproduce it (without EXT:realurl) reopen it or open a new issue with a reference to this one. Thank you.

Actions

Also available in: Atom PDF