*bump, I'd be curious to know the answer for this one too.

I wrote my own 404 handler where I react on the language and position in the tree and return true if I found a node which handles the specific node/language. Definitions on what to chosse are stored in an xml config file.

@Thomas, care to share those mad skills? any source we can sneek a look at anywhere?

Here is a simple peace of code which demonstrates the usage. You can also react on the Browser language settings or all other HTTP headers:

Snippet

using System;
using System.Web;
using umbraco.BusinessLogic;
using umbraco.interfaces;
 
namespace MyLibrary.Handler
{
    public class NotFoundTestHandler: INotFoundHandler
    {
 
        private bool cacheUrl;
 
        private int redirectId;
 
 
        public bool Execute(string url)
        {
            try
            {
                var server = HttpContext.Current.Request.ServerVariables["SERVER_NAME"];
                var referrer = "";
                if (HttpContext.Current.Request.UrlReferrer != null)
                    referrer = HttpContext.Current.Request.UrlReferrer.ToString();
 
                if (server == null)
                    server = "";
                if (url == null)
                    url = "";
 
                var completeUrl = server + "/" + url;
                Log.Add(LogTypes.NotFound, 0, "MyNotFoundHandler: " + completeUrl + " || Referrer: " + referrer);
 
 
                if (completeUrl.StartsWith("www.mydomain1.com/en"))
                {
                    redirectId = GetMyEnNodeID;
                    return true;
                }
                if (completeUrl.StartsWith("www.mydomain1.com/de"))
                {
                    redirectId = GetMyDeNodeId();
                    return true;
                }
                return false;
            }
            catch (Exception ex)
            {
                Log.Add(LogTypes.Error, 0,
                        "MyLibrary.Handler.NotFoundTestHandler: " + ex.Message + "\n\n" + ex.StackTrace);
                return false;
            }
        }
 
        public bool CacheUrl
        {
            get { return cacheUrl; }
        }
 
        public int redirectID
        {
            get { return redirectId; }
        }
    }
}

hth, Thomas

Hi Bjorn,

The structure of the error pages should be like this...

<errors>
    <error404>
        <errorPage culture="default">1</errorPage>
        <errorPage culture="nl-NL">1245</errorPage>
    </error404>
</errors>

Just checking, is that what you had?

A NotFoundHandler, like Thomas's one, is the way I'd go about doing it.  But I've been using a version from a code snippet I found in an old Umbraco book:

http://umbraco.org/documentation/books/not-found-handlers/creating-a-custom-not-found-handler

It lets you control the 404 page within Umbraco, via a content picker data-type.

Good luck, Lee.

Hi Lee,

that's exactly what we have, yes. Even though we've got the hostname set up to Dutch (Netherlands), it keeps going to whatever pageId we enter in the 'default' entry. Very curious.

Thomas: thanks for your insights and code. Might have to look into implementing something similar in future projects.

Bjorn, any solution as to why it is just going to the default entry?

Seth,

we've had no luck getting this to work as it should out of the box. Ultimately resulted to some custom programming as suggested above.

Sorry I have no better news for you.

is working on a reply...