CODEWITHSUNDEEP
asp.neturl-routingumbraco
CodeMonkey
CodeMonkey

Reputation: 3668

Umbraco and dynamic URL content at root level

I need to port a website to asp.net and decided to use Umbraco as the underlying CMS.

The issue I'm having is I need to retain the URL structure of the current site.

The current URL template looks like the following 

domain.com/{brand}/{product}

This is hard to make a route for since it mixes in with all the other content on the site. Like domain.com/foo/bar which is not a brand or product.

I've coded up a IContentFinder, and injected it into the Umbraco pipeline, that check the URL structure and determins if domain.com/{brand} matches any of the known brands on the site, in which case i find the content by its internal route domain.com/products/ and pass along {brand}/{model} as HttpContext Items and return it using the IContentFinder.

This works, but it also means no MVC controller is called. So now I'm left with fetching from the database in the cshtml file which is not so pretty and kind of breaks MVC conventions.

What i really wan't is to take the url domain.com/{brand}/{product} and rewrite it to domain.com/products/{brand}/{product} and then being able to hit a ProductsController serving up the content based on the parameters brand and product.

Upvotes: 0

Views: 1393

Answers (1)

mortenbock
mortenbock

Reputation: 671

There are a couple of ways to do this.

It depends a bit on your content setup. If your products exist as pages in Umbraco, then I think you are on the right path.

In your content finder, remember to set the page you've found on the request like this request.PublishedContent = content;

Then you can take advantage of Route Hijacking to add a ProductController that will get called for that request: https://our.umbraco.org/Documentation/Reference/Routing/custom-controllers

Example implementation:

protected bool TryFindContent(PublishedContentRequest docReq, string docType)
{
    var segments = docReq.Uri.GetAbsolutePathDecoded().Split(new[] {'/'}, StringSplitOptions.RemoveEmptyEntries);
    string[] exceptLast = segments.Take(segments.Length - 1).ToArray();

    string toMatch = string.Format("/{0}", string.Join("/", exceptLast));

    var found = docReq.RoutingContext.UmbracoContext.ContentCache.GetByRoute(toMatch);
    if (found != null && found.DocumentTypeAlias == docType)
    {
        docReq.PublishedContent = found;
        return true;
    }

    return false;
}

public class ProductContentFinder : DoctypeContentFinderBase
{
    public override bool TryFindContent(PublishedContentRequest contentRequest)
    {
        // The "productPage" here is the alias of your documenttype
        return TryFindContent(contentRequest, "productPage");
    }
}

public class ProductPageController : RenderMvcController {}

In the example the document type has an alias of "productPage". That means that the controller needs to be named exactly "ProductPageController" and inherit the RenderMvcController.

Notice that it does not matter what the actual pages name is.

Upvotes: 1

Related Questions