Bug #25290
closed
wrong 404-handling when TYPO3_CONF_VARS['FE']['pageNotFound_handling'] is empty
Added by Michael Bakonyi about 13 years ago.
Updated almost 9 years ago.
Description
Maybe since 4.5 the error-handling doesn't act as stated in the INSTALL TOOL anymore. If TYPO3_CONF_VARS['FE']['pageNotFound_handling'] is empty there should be a redirect up to the next accessible page within the rootline. Currently it acts like TYPO3_CONF_VARS['FE']['pageNotFound_handling'] was set to '1' – so there's always an error message. I think the problem's in line 1027 ++ in class.tslib_fe.php
(issue imported from #M17903)
- Category deleted (
Communication)
- Target version deleted (
0)
Hi Michael,
are you sure the mentioned code piece in getPageAndRootline() is really executed? Although the way how error messages are generated has changed, the code always interrupted the execution at this point (at least in 4.4).
You're using RealURL, aren't you? Maybe there something has changed?
I wonder, how The next visible page upwards in the page tree is shown. should work with IDs, as you never know, where a non-existant page might be located..
Could you try a 4.3/4.4 with an older RealURL version, please?
Thanks
Steffen
When I've time to test I'll do it + give you feedback!
- Status changed from New to Needs Feedback
- Is Regression set to No
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (6.2.3)?
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.
the bug still exists in typo3 6.2.14 ...
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by