I fixed my issue - it is caused by this bug in Umbraco.Web.Mvc.RenderRouteHandler:

    internal virtual RouteDefinition GetUmbracoRouteDefinition(RequestContext requestContext, PublishedContentRequest publishedContentRequest)
    {
        var defaultControllerType = DefaultRenderMvcControllerResolver.Current.GetDefaultControllerType();
        var defaultControllerName = ControllerExtensions.GetControllerName(defaultControllerType);
        //creates the default route definition which maps to the 'UmbracoController' controller
        var def = new RouteDefinition
            {
                ControllerName = defaultControllerName,
                ControllerType = defaultControllerType,
                PublishedContentRequest = publishedContentRequest,
                ActionName = ((Route)requestContext.RouteData.Route).Defaults["action"].ToString(),
                HasHijackedRoute = false
            };

        //check that a template is defined), if it doesn't and there is a hijacked route it will just route
        // to the index Action
        if (publishedContentRequest.HasTemplate)
        {
            //the template Alias should always be already saved with a safe name.
            //if there are hyphens in the name and there is a hijacked route, then the Action will need to be attributed
            // with the action name attribute.
            var templateName = publishedContentRequest.TemplateAlias.Split('.')[0].ToSafeAlias();
            def.ActionName = templateName;
        }

        //check if there's a custom controller assigned, base on the document type alias.
        var controllerType = _controllerFactory.GetControllerTypeInternal(requestContext, publishedContentRequest.PublishedContent.DocumentTypeAlias);

        //check if that controller exists
        if (controllerType != null)
        {
            //ensure the controller is of type 'IRenderMvcController' and ControllerBase
            if (TypeHelper.IsTypeAssignableFrom<IRenderMvcController>(controllerType)
                && TypeHelper.IsTypeAssignableFrom<ControllerBase>(controllerType))
            {
                //set the controller and name to the custom one
                def.ControllerType = controllerType;
                def.ControllerName = ControllerExtensions.GetControllerName(controllerType);
                if (def.ControllerName != defaultControllerName)
                {
                    def.HasHijackedRoute = true;
                }
            }
            else
            {
                LogHelper.Warn<RenderRouteHandler>(
                    "The current Document Type {0} matches a locally declared controller of type {1}. Custom Controllers for Umbraco routing must implement '{2}' and inherit from '{3}'.",
                    () => publishedContentRequest.PublishedContent.DocumentTypeAlias,
                    () => controllerType.FullName,
                    () => typeof(IRenderMvcController).FullName,
                    () => typeof(ControllerBase).FullName);
                //exit as we cannnot route to the custom controller, just route to the standard one.
                return def;
            }
        }

        //store the route definition
        requestContext.RouteData.DataTokens["umbraco-route-def"] = def;

        return def;
    }

The route handler does a check to see if there is a controller with a matching name to the document type - it has some special handling for this case that I was not aware of. If you have a Document Type with an Alias that is the same as one of your controllers (e.g. Registration + RegistrationController) this error occurs because of the early-exit in the else block that skips the line adding the RouteDefinition to the data token dictionary.

Thanks That saved me a lot of messing around :)

hey everybody

I'm having the same problem with the RedirectToCurrentUmbracoPage() and I came across this post but not really sure what to do with it.. . . Alex can you please elaborate more on this subject?

Where should I put the code you wrote in the earlier post?

Greetings

is working on a reply...