All project content is available for reading, but you need to be a member of the project for Subversion checkout of source code, or to create/modify any information.
Login if you are a member. Apply here to request membership (open to all).

Ticket #273 (closed defect: wontfix)

Opened 10 years ago

Last modified 10 years ago

Default language always shown

Reported by: chrislar@… Owned by: mari@…
Priority: major Component: 404Handler
Keywords: Cc:

Description (last modified by chrislar@…) (diff)

I'm experiencing problems with the 404handler.

If I try to navigate to a page that doesn't exist, ex. http://www.mypage.com/en/About/, I get the english errorpage as expected.

However, if I try to view a german page that doesn't exist, http://www.mypage.com/de/About/, I still get the english errorpage.

<%= CurrentPage.LanguageBranch %> in 404NotFound.aspx always returns "en"

Is there something wrong with my configuration of languages on the site, or is this a fault in the 404handler? I have tried installing the handler through NuGet on several multilanguage sites, and am experiencing the same behaviour on all of them.

Change History

comment:1 Changed 10 years ago by chrislar@…

  • Type changed from question to defect

comment:2 Changed 10 years ago by chrislar@…

  • Description modified (diff)

comment:3 Changed 10 years ago by steve@…

  • Status changed from new to closed
  • Resolution set to wontfix

There is no language detection for resources that are not found. The About page shown above does not exist, so we cannot know which language it was ment for. What language should we show for a pdf file not present in the upload directory?

However, in the url above, the language is actually present, and a workaround could be to parse this (the first url fragment) and from that look up and set the ui culture of the 404 page.

Also, if language is matched against domain name (.com / .no), I think the correct language will be used.

Some of the sites where the module is in use show the page in several different languages (on the same page), to make sure everyone gets the message.

comment:4 Changed 10 years ago by chrislar@…

Ok, thanks for the reply. Guess I just expected it would use a specific language based on the language-part of the URL, and use default-language if not found (first URL fragment not matching any language in EPiServer.DataAbstraction.LanguageBranch.ListEnabled()).

This would be handy not only to show the error-message in the correct language, but also having other elements such as the menu shown in the correct language.

Note: See HelpUser/Tickets for help on using tickets.