Throwing FrontendPageNotFoundException breaks
A bug in 2.2, submitted by michael-e on 23 February 2011
Announcement
Symphony's issue tracker has been moved to Github.
Issues are displayed here for reference only and cannot be created or edited.
Browse
Closed#576: Throwing FrontendPageNotFoundException breaks
Can you reproduce this issue in a normal install that is not using the default workspace?
Is the datasource excluded from the 404 page (otherwise that’ll infinite loop).
I ask because I can’t reproduce this issue at all.
I created a new datasource and choose it to get an entry with a system id of 111111 (doesn’t exist), then redirect to 404 page option.
I’ve tried with and without a 404 page type set, and in both instances this works.
Is the datasource excluded from the 404 page (otherwise that’ll infinite loop).
You hit the bull’s eye! My bad.
Sorry for this. I suggest to close this bug.
This issue is closed.
Throwing a FrontendPageNotFoundException breaks if an event or datasource is attached to a page using Symphony’s (appropriate) delegates.
This issue breaks, for example, the native datasource functionality “Redirect to 404 page when no results are found”.
A simple test for this issue is described in a post regarding the Global Resource Loader extension.