Hi Harry,

You could use one of the special reserved property aliases - either umbracoRedirect or umbracoInternalRedirectId to set a redirect from the Car 1 node to the Features node.

The main problem with this is that you have to manually select the node to redirect to.  Guess that depends on how much content you are going to have.

Another way would be to set a template on the Car 1 node that does a Response.Redirect to the first child node?

Cheers, Lee.

I usualy use a .NET user control macro. I can either drop it in a template, or allow the user to drop it into a rich text area. I don't have a package for it, but my codebehind (which contains everything) is as follows:

using System;
using System.Web;
using umbraco.presentation.nodeFactory;

namespace UserControls
{
    public partial class RedirectControl : System.Web.UI.UserControl
    {
        public bool RedirectToUrl { get; set; }
        public string RedirectUrl { get; set; }
        public bool RedirectToPage { get; set; }
        public int RedirectPage { get; set; }
        public bool RedirectToFirstChild { get; set; }
        public bool IsPermanent { get; set; }

        protected void Page_Init(object sender, EventArgs e)
        {
            if (RedirectToUrl)
                DoRedirect(RedirectUrl);

            if(RedirectToPage)
                DoRedirect(FullyQualifiedApplicationPath + umbraco.library.NiceUrl(RedirectPage).TrimStart('/'));

            if(RedirectToFirstChild)
            {
                var currentNode = Node.GetCurrent();
                if (currentNode.Children != null && currentNode.Children.Count > 0)
                    DoRedirect(FullyQualifiedApplicationPath + umbraco.library.NiceUrl(currentNode.Children[0].Id).TrimStart('/'));
            }
        }

        protected void DoRedirect(string url)
        {
            if (!IsPermanent)
            {
                Response.Redirect(url, true); // 302 Found
            }
            else
            {
                Response.Clear();
                Response.Status = "301 Moved Permanently";
                Response.AddHeader("Location", url);
                Response.End();
            }
        }

        protected string FullyQualifiedApplicationPath
        {
            get
            {
                var appPath = "";

                var context = HttpContext.Current;
                if (context != null)
                {
                    appPath = string.Format("{0}://{1}{2}{3}",
                        context.Request.Url.Scheme,
                        context.Request.Url.Host,
                        (context.Request.Url.Port == 80) ? string.Empty : ":" + context.Request.Url.Port,
                        context.Request.ApplicationPath);
                }

                if (!appPath.EndsWith("/"))
                    appPath += "/";

                return appPath;
            }
        }
    }
}

Allows you to redirect to a url, specific page id, or the first child. Additionaly you can decide whether the redirect is perminant or not.

Matt

Hi Guys,

Thanks for your replies. The only downside of this is I have to manually pick the document to where I need to be redirected, theres no automated way?

Regards,

Harry

Hey Harry

My macro control has the option to redirect to first child. This is worked out dynamicly, so if you reorder the children, it will automatically update.

Matt

Hi Matt,

even if your control does the job in the eyes of the end user I believe that it's not right to send Redirect headers again and again. Your control is perfect to be used in conjunction with another macro (xslt or user control) that will render the correct Urls in the menus.

Even with the umbracoInternalRedirectId that Lee proposed there will be a problem. This is because /Car1.aspx and Car1/Features.aspx will render the same content. This means that you will get a duplicate content warning from Google web-master tools.

@Dimitris: IMO, sending redirect headers isn't that much of an overhead.  The duplicate content (for Google) isn't a problem either... Harry could include a canonical link in the meta data. (ref)

@Harry: There can be an automated way, but you'd need to hook into one of the Publish events in the API - to set the value of "umbracoInternalRedirectId" (or "umbracoRedirect") for the car type (hopefully you've got a separate doc-type for those pages?)

If you don't want to get your hands dirty with the API code, then Matt's redirect macro is the way to go.  Add it to the template for the car type (or create a new one for them), include the redirect macro ... and set that template as the default for the car type doc-type, (again that is if you have a separate doc-type for those pages?)

Edit: One last thing, about Dimitris's solution. Its recommend that you do not use inline .NET scripts in your XSLT files. It's bad practice, apart from that it wont work in Medium Trust and other security reasons - it will also create a new temporary compiled class for each and every page-load/request.  These will be stored in the "Temporary ASP.NET Files" folder (default location: "%SystemRoot%\Microsoft.NET\Framework\versionNumber\Temporary ASP.NET Files")

Unless you regularly clean-out that folder, depending on your traffic - your hard-disk space can soon fill-up.  I'm not scaremongering, just letting you know your options.

Cheers, Lee.

Hi Lee,

The first several post works fine. I don't want to get my hands dirty with the umbraco API. I'll go to that place in the near future. 

Again guys, thank you so much!

Regards,
Harry

is working on a reply...