Project

General

Profile

Actions

Bug #86260

closed

Site error handling: Show content from page with / entry point

Added by Benjamin Robinson over 5 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Target version:
-
Start date:
2018-09-15
Due date:
% Done:

0%

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

Description

The option "Show Content from Page" in the Site Configuration does not work if the "Entry point" is set to "/" instead of "https://www.mydomain/".
(Version: TYPO3 9.4.0)


Related issues 2 (0 open2 closed)

Related to TYPO3 Core - Bug #86935: Cannot fetch 404 page with simple baseClosed2018-11-15

Actions
Has duplicate TYPO3 Core - Bug #86616: Content of 404 page is not shownClosed2018-10-10

Actions
Actions #1

Updated by Georg Ringer over 5 years ago

  • Status changed from New to Accepted
Actions #2

Updated by Martin Reimund over 5 years ago

  • PHP Version set to 7.2

Problem also appears in TYPO3 CMS v9.5.

It occurs in frontend and brings you to a white empty page once you have configured an error handler with the option "Show content from page" and specified a typo3 page as result of the error handler. Use an external link as result of an error handler basically works only as long you pass a protocol and hostname.

How have I produced this?
I have configured an error handler in the backend site management module "sites" for the case that a typo3 page is not found (http status code 404). I have used the option "Show content from page" (field "How to handle errors") and specified a typo3 page (typo link) in the field "Show Content From Page" as result of the error handler. As soon a frontend page request leads to a "page not found" (http status code 404), it tries to show the specified page, but the result is a white empty page instead of the specified one though.

I have taken a look into it and dove through the code to find out what causes the problem. It seems like the underlying cause is the class "PageContentErrorHandler". This page error handler uses the resource fetching method "GeneralUtility::getUrl". In this certain case the method gets passed a path without protocol and hostname, but it seems like this method requires this both fragments to be passed though.

Actions #3

Updated by Martin Reimund over 5 years ago

  • Related to Bug #86616: Content of 404 page is not shown added
Actions #4

Updated by Martin Reimund over 5 years ago

  • Related to deleted (Bug #86616: Content of 404 page is not shown)
Actions #5

Updated by Martin Reimund over 5 years ago

  • Has duplicate Bug #86616: Content of 404 page is not shown added
Actions #6

Updated by Riccardo De Contardi about 5 years ago

  • Related to Bug #86935: Cannot fetch 404 page with simple base added
Actions #7

Updated by Riccardo De Contardi about 4 years ago

  • Status changed from Accepted to Needs Feedback

This should have been fixed with #86935 - I tried the following short test with TYPO3 9.5.15 and the following configuration (only relevant part shown):

base: '/'
baseVariants: {  }
errorHandling:
  -
    errorCode: '404'
    errorHandler: Page
    errorContentSource: 't3://page?uid=235'

rootPageId: 1
routes: {  }
and after calling a non-existent url, the page uid=235 has been shown

therefore I think that the issue has been solved. Am I missing something or is a different test necessary?

Actions #8

Updated by Jonas Eberle about 4 years ago

Works for me, too (v9 + v10)

Actions #9

Updated by Benjamin Robinson about 4 years ago

It works for me, too. I think it can be closed.

Actions #10

Updated by Riccardo De Contardi about 4 years ago

  • Status changed from Needs Feedback to Closed

@Ben Robinson thank you very much for your patience and quick reply;

I close this issue as resolved.

If you think that this is the wrong decision or experience the issue again, please reopen it or open a new issue with a reference to this one and a step-by-step guide about how to reproduce it. Thank you again.

Actions

Also available in: Atom PDF