TYPO3 Core

Oki, but it's correct.

Hide at login = hidden page

hidden page = not visible for visitor

If you want a good process, do not redirect user to HIDE TO LOGIN page, but to visible or page NOT IN MENU

I don't if my english is correct, but now i'm sure that 404 process is correct.

thank you for dimitry's work !

@Benni Mack

I tried the following tests with TYPO3 9.5.5

Test1 - setup¶

1. Fresh TYPO3 installation
2. Create a minimal setup for frontend users as following
   1. create a FE usergroup "TEST1"
   2. create a FE usergroup "TEST2"
   3. create a FE user "test" and assign it to "TEST1"
3. Create the following pages
   1. Create a page called "404 Error"
   2. Create a page called "403 Error"
   3. Create a page called "forbidden page" and assign it the FE usergroup "TEST2"
4. Edit the site configuration
   1. Error Handling > Create new
      1. HTTP Status Code: 404
      2. How to handle error: Show content from Page
      3. Show content from page: select "404 Error"
   2. Error Handling > Create new
      1. HTTP Status Code: 403
      2. How to handle error: Show content from Page
      3. Show content from page: select "403 Error"

Test 1 - execution (executed with Chrome in incognito mode)¶

Test 2 - setup¶

1. same as Test 1
2. "404 Error" page >
   1. create a CE "Headline",
      1. call it "I AM NOT LOGGED IN"
      2. set Access > "Hide at Login"
   2. create a CE "Headline",
      1. call it "I AM LOGGED IN"
      2. set Access > "Show at any Login"
3. "403 Error" page >
   1. create a CE "Headline",
      1. call it "I AM NOT LOGGED IN"
      2. set Access > "Hide at Login"
   2. create a CE "Headline",
      1. call it "I AM LOGGED IN"
      2. set Access > "Show at any Login"

Test 2 - Execution¶