Issue Bug Closed

#55378"Showing" page type -Menu Separator- results in Uncaught Exception

Paul A. Auwehla 01/28/14, 09:19 updated 06/02/14, 16:58

Description

Try to “show” a page of type “Menu Separator”.
(Which is of cause not the way this page type is made for)

Result:
Uncaught TYPO3 Exception
#1301648781: The requested page does not exist!

This is not a very polite answer when trying
to show a page out of its content menu.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 7

  1. Georg Ringer commented and changed status New Needs Feedback 01/28/14, 10:18

    but what do you expect then? this is the same if trying to display a sysfolder.

    if you have a proper exceptionhandler or handle not found pages, you will get a nicer response as well

  2. Paul A. Auwehla commented 01/28/14, 10:35

    If I try to show a SysFolder I get the starting page.
    This would be a kind and nice response.

  3. Alexander Opitz commented 01/28/14, 11:59

    Did you try to search on google for a solution?

    If not, try “typo3 pageNotFound_handling” as search terms.

  4. Paul A. Auwehla commented 01/28/14, 15:29

    Trying to show a page from the content-menu of the backend
    should not belong to a page-not-found-404-handling used
    to handle the frontend of typo3.

    In fact these pages of type “sysfolder” or “menu-separator”
    are existing for the backend-users trying to show them ;-)

    Trying to show a sysfolder results in showning the starting
    page of a website.

    Trying to show a page of type menu-separator could result
    to the same – and not in showing a “Uncaught TYPO3 Exception” -
    which is not really elegant, isnt it?

  5. Alexander Opitz commented 01/29/14, 08:15

    This depends on your configuration of exceptionhandler or the page not found handler.

  6. Georg Ringer commented 01/29/14, 08:53

    there are many ways how you don’t get the desired page in the FE, even if it perfectly exists in FE! e.g. if you limit the access to a user group in the BE … so this is perfectly fine

  7. Alexander Opitz commented and changed status Needs Feedback Closed 06/02/14, 16:58

    No feedback within the last 90 days => closing this ticket.

    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.