Bug #88957
closed
ID was not an accessible page - on hidden pages although the 404 error handler is configured in the site config
0%
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?
Updated by Anja Leichsenring about 5 years ago
- Related to Bug #89006: Page unavailable exception is thrown when the root page if fe group protected added
Updated by Riccardo De Contardi about 5 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.
Updated by Susanne Moog over 4 years ago
- Related to Bug #86346: Hidden pages sent 403 Header added
Updated by Susanne Moog over 4 years 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.