Quantcast
Channel: Using Optimizely Platforms
Viewing all articles
Browse latest Browse all 8020

product on multiple urls, with different content but coming from a single product node

$
0
0

I am working on the episerver rebuild of a sitecore e-commerce website for a client and i am not sure how to recreate a particular piece of functionality they have. In their current site they can create a type of content node that works as a sort of wildcard for requests for product urls.

For instance, an editor could create a tree structure like this:

  • Home1
    • Shop
      • Product

And then any request to “home1/shop/*” will go to the controller for ‘Product’ (such as “home1/shop/productOne”, “home1/shop/productTwo”).

They also need to do the same for different sites within the same solution, so a simplified version of the content tree would be:

  • Home1
    • Shop
      • Product
    • Home2
      • Shop2
        • Product

So that any request to “home1/shop/*” and “home2/shop2/*” will go to the relevant controller. This means that both “home1/shop/productOne” and “home2/shop2/productOne” will return the product page but a url like “home2/shop3/productOne” will return a 404.

To be clear these two pages will show slightly different versions of the content for the product, so it is not just a case of a product being available in two different urls.

In addition this routing can’t be hard coded because it is based on the content type of the nodes. It must still be possible for an editor to create this in the content tree:

  • Home1
    • Shop
      • Product
    • Shop2
      • Product

and then for a request to “home1/shop2/*” to return the correct product details.

does anyone know how best to receate this in episerver?


Viewing all articles
Browse latest Browse all 8020

Trending Articles