@infograf768
I think this has been reported before (but i did not find the issue / discussion)

Not sure I understand.

If you try to build a SEF URL that contains &Itemid=NNN
and NNN menu item is the home page menu item for language ALL

why would you try to build a URL with an itemid which no one should use?

Please be nice to me and give precise instructions to test with core to reproduce your issue.

Soon, I ll update the description of this issue with precise instructions,
using an example with core components

FYI, I found an issue that does not look exactly related to what you describe but is nevertheless frustrating.

Set the Home page tagged to ALL languages as a Smart Search menu item.
Then add a Smart Search module wherever on site (language is not important).

Try to search anything => as the smart search menu item is set to the Home set to ALL, one can't get the search results. One remains on the same page.

(Note: choosing an itemid in the module to another page than that home has no effect )

Sorry for not updating description earlier

I have updated description with a picture from duplicate issue #21448
to see the issue just create the setup that you see in the picture

• Type of components is not important,
• important is to have different components

and you will get either wrong page shown (if you are "lucky") or usually a 404 error

I understand that this configuration is not common,
but it should at least be documented that using a different type of menu item for home page ALL will not work,

then if someone is willing to spend time at the router, i have linked to the code that creates the issue, sorry i cannot spend time for this now

I have opened this issue , because it was originally reported as bug in our component , so i did spend already 2 hours tracking down the issue

Tested here with Home tagged to ALL as a Newsfeed menu item and Languages Home are content.
No p.

I still do not fully understand your issue.
To me, it looks like we can get issues only when the Home tagged to ALL menu item may be needed by another component or module which is reached via Content Language and such a menu item type does not exist for these Content Languages.
Example the Smartsearch above or a Login form.

But you are not supposed to ever be using a home page item of ALL are you?

I am closing this

I don't know if something, has changed since i opened this,

but do not want to go looking around now
as this does not seem easy to replicate or some other work made it harder to occur
or even fixed it completely in very recent versions

i will watch for it, and if i come across it again i will reopen it, with more details