Bug #88957

ID was not an accessible page - on hidden pages although the 404 error handler is configured in the site config

Added by Denis Mir about 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2019-08-14
Due date:
% Done:

0%

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

Description

On pages that are configured "hidden" in the page properties users get a "Page Not Found Reason: ID was not an accessible page" error except getting the configured 404 error page.

In the site config we have something like:

errorHandling:
  -
    errorCode: '404'
    errorHandler: Page
    errorContentSource: 't3://page?uid=22'

So the error handler is configured correctly. But on hidden pages it is not thrown correctly. For pages that do really not exist the correct error page is shown. (ID 22)

Is it our configuration error or is it a bug?


Related issues

Related to TYPO3 Core - Bug #89006: Page unavailable exception is thrown when the root page if fe group protectedClosed2019-08-23

Actions
Related to TYPO3 Core - Bug #86346: Hidden pages sent 403 HeaderUnder Review2018-09-21

Actions
#1

Updated by Anja Leichsenring about 2 years ago

  • Related to Bug #89006: Page unavailable exception is thrown when the root page if fe group protected added
#2

Updated by Riccardo De Contardi almost 2 years ago

I performed a test with 9.5.11

1) The site configuration config.yaml contains (relevant part):

errorHandling:
  -
    errorCode: '404'
    errorHandler: Page
    errorContentSource: 't3://page?uid=51'
  -
    errorCode: '403'
    errorHandler: Page
    errorContentSource: 't3://page?uid=52'

2) I created a page, set it to hidden
3) With a different browser (incognito mode) , I tried to access the hidden page

Current results

The 403 page is shown.

If I remove the setting about 403 error in the config.yaml file I get the error:

Page Not Found
Reason: ID was not an accessible page

Expected result

The 404 page should be shown

Note

When using a different setting on point 2):

2) I created a page, set its "start date" to the future

the result is the same.

#3

Updated by Susanne Moog over 1 year ago

  • Related to Bug #86346: Hidden pages sent 403 Header added
#4

Updated by Susanne Moog over 1 year ago

  • Status changed from New to Closed

Please continue / see issue #86346 - the problem here is that hidden pages send a 403 instead of a 404 error.

Also available in: Atom PDF