Issue Bug Closed

#86805Page not found error when rootpage (or first level pages) is hidden

Jan Kornblum 10/30/18, 18:11 updated 01/06/22, 09:36

Description

In an multidomain instance, calling an (hidden) rootpage or first level page causes an page not found error.

Setup:

- Start (Shortcut)
--- Domain 1 (has site configuration)
------ Item 1
------ Item 2 (hidden) <-- calling from BE not possible (page not found error)
------------ Item 2.1 (hidden) <- calling from BE possible
--- Domain 2 (has site configuration, hidden) <-- calling from BE not possible (page not found error)
------ Item 1
------ Item 2 (hidden) <-- calling from BE not possible (page not found error)

Reviews 0

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

History 5

  1. Jan Kornblum changed category 11/01/18, 11:03

  2. Georg Ringer commented and changed status New Needs Feedback 03/05/20, 14:55

    Hi,

    so which domains are you using for the backend? a different then the ones from the 2 sites?

  3. Jan Kornblum commented 03/06/20, 01:36

    Georg Ringer wrote:
    > Hi,
    >
    > so which domains are you using for the backend? a different then the ones from the 2 sites?

    No different one, just any of the 2 sites…

  4. Benni Mack commented 01/14/21, 15:07

    Hey Jan,

    I cannot reproduce this issue at all, can you please re-check? Works fine for root-level for previewing when the cookie (be_typo_user) is set.

  5. Benni Mack commented and changed status Needs Feedback Closed 01/06/22, 09:36

    Closing this issue due to lack of feedback.