Bug #87969

Page route for translated page is not generated correctly when page has frontend group access restrictions

Added by Helmut Hummel about 2 years ago. Updated 11 months ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Target version:
-
Start date:
2019-03-20
Due date:
% Done:

100%

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

Description

The URI Builder fetches the slug field of the target page to generate the URI.
This works also for pages with frontend group access restrictions, because PageRepository::getPage is called with disableGroupCheck.

However when a translated page should be fetched, the disableGroupCheck argument is not pushed through the query which fetches the translation,
which leads to the situation that the translation is not found and the slug of the default language page is used. In the end this leads to a wrongly composed URL.

To reproduce:

  1. Create a page
  2. Translate the page to another language
  3. Add frontend group access restriction to page in default language
  4. Preview translated page (preview button of translated page)

Related issues

Related to TYPO3 Core - Bug #86653: Preview of page, with "show", not working when starttime is setClosed2018-10-14

Actions
Related to TYPO3 Core - Bug #90842: FE user restriction on pages and link incl. linkAccessRestrictedPages create wrong URLsClosed2020-03-26

Actions
Has duplicate TYPO3 Core - Bug #91045: Language overlay does not respect $disableGroupAccessCheckClosed2020-04-15

Actions

Also available in: Atom PDF