Bug #26484: extend to subpages in page properties in access tab does not work correctly - TYPO3 Core - TYPO3 Forge

Custom queries

12 LTS
Accessibility
Dashboard issues
Easy tasks
Extbase Issues
FAL Issues
FAL Sprint 2023
Hierarchical Issues
Issues reported for v11
JavaScript issues
JavaScript Issues (w/o Epics/Stories)
Most wanted Bugfixes
Most wanted Features
My open issues
New & Unassigned
No feedback within 90 days
Open Bugs
Open issues of 10
Page Tree Regressions after 2020-07-28
Recently modified
Regressions
Stabilization Issues
Usability or UX

Watchers (4)

Kaloyan Chernev
Riny van Tiggelen
Roman Eberle
Stephan Großberndt

Actions

Copy link

Bug #26484

closed

extend to subpages in page properties in access tab does not work correctly

Added by Simon Schaufelberger almost 13 years ago. Updated about 4 years ago.

Status:

Closed

Priority:

Must have

Assignee:

Category:

Frontend

Target version:

Start date:

2011-04-29

Due date:

% Done:

Estimated time:

TYPO3 Version:

4.5

PHP Version:

Tags:

Complexity:

medium

Is Regression:

Sprint Focus:

Description

I have a page structure like this:

-Page
 - Page (access restricted including subpages)
  - Page (x)
 - Login page

now when i call page x directly from the backend without being logged in, i still see the page but not the content. Only if i set the page x also as restriced page (set a usergroup to it), THEN i get a redirect to the login page.

TYPO3 4.5.2

Related issues 2 (1 open — 1 closed)

Related to TYPO3 Core - Bug #15984: menu.showAccessRestrictedPages doesn't replace link for "include subpages"

Accepted

2006-04-05

Actions

Related to TYPO3 Core - Bug #78825: Wrong pid determination when opening a nested access restriced page

Closed

2016-11-28

Actions

Issue # Delay: days Cancel

History
Notes
Property changes

Actions

Copy link

Updated by Andreas Wolf over 12 years ago

Category set to Content Rendering
Status changed from New to Needs Feedback
Complexity set to medium

Is this still valid with the latest core version?

Actions

Copy link

Updated by Simon Schaufelberger over 12 years ago

At the moment i cannot even reproduce it again with 4.5.2. It was one of our plenty websites... Maybe it has to do with the pageNotFound_handling settings

Actions

Copy link

Updated by Stephan Großberndt over 11 years ago

I have a problem that is related, if its not the same:

- TYPO3 4.5.22 (default settings for page not found)

$TYPO3_CONF_VARS['FE']['pageNotFound_handling'] = ''

- realurl 1.12.3 (default settings for page not found)

$TYPO3_CONF_VARS['EXTCONF']['realurl']['_DEFAULT'] = array(
    'init' => array(
        'enableCHashCache' => 1,
        'enableUrlDecodeCache' => 1,
        'enableUrlEncodeCache' => 1,
        'appendMissingSlash' => 'ifNotFile',
    ),

I have a page structure like this:

root
 - homepage
  - sysfolder
   - access restricted page (including sublevels)
    - page X

When you re-access page X after having been logged out, TYPO3 serves an empty page - which is the content of sysfolder! (checked by dumping $TSFE->id in index_ts.php).

As far as I can figure it out: TYPO3 sees the access restriction and starts walking the tree to root until it finds a page that is not access restricted - but does not take into account that sysfolders do not have content to display and therefore should not be served.

Actions

Copy link

Updated by Maarten Mandemaker about 11 years ago

Bug confirmed (TYPO3 6.0.2)

Redirection to (login)page only works when accessing a page which has explicit access rights. It does not work when the page inherits the access conditions from a higher level (extend to subpages checkbox).

Actions

Copy link

Updated by Jigal van Hemert almost 11 years ago

Category deleted (~~Content Rendering~~)
Status changed from Needs Feedback to New

Actions

Copy link

Updated by Philipp Gampe over 10 years ago

Category set to Frontend
Status changed from New to Accepted

Actions

Copy link

Updated by Alex no-lastname-given about 10 years ago

Bug exists in TYPO3 6.1.7 also

Actions

Copy link

On version 9.5.14 and 10.4.0-dev (latest master), if I try to access a subpage of a restricted page (*) directly from the backend, I get a "page not found" error (403 If I am not wrong).

(*) Note: the restricted page has

- is restricted
-has "extend to subpages" checked

Actions

Copy link

#19

Updated by Susanne Moog about 4 years ago

Status changed from Accepted to Closed

As verified by Riccardo this is fixed in newer versions.

Actions

Copy link

Also available in: Atom PDF

Project

General

Profile

TYPO3 Core

Custom queries

Watchers (4)

Bug #26484

extend to subpages in page properties in access tab does not work correctly

Updated by Andreas Wolf over 12 years ago

Updated by Simon Schaufelberger over 12 years ago

Updated by Stephan Großberndt over 11 years ago

Updated by Maarten Mandemaker about 11 years ago

Updated by Jigal van Hemert almost 11 years ago

Updated by Philipp Gampe over 10 years ago

Updated by Alex no-lastname-given about 10 years ago

Updated by Simon Schaufelberger about 10 years ago

Updated by Dimitri König about 9 years ago

Updated by Riny van Tiggelen over 8 years ago

Updated by Riccardo De Contardi almost 7 years ago

Updated by Riccardo De Contardi almost 7 years ago

Updated by Riccardo De Contardi almost 7 years ago

Updated by Riccardo De Contardi almost 7 years ago

Updated by Riccardo De Contardi almost 7 years ago

Updated by Riccardo De Contardi about 4 years ago

Updated by Susanne Moog about 4 years ago