Vulnerability in EPiServer.Forms

Try our conversational search powered by Generative AI!

Multi-venue Site Setup

Vote:
 

Hi guys,

I am brand new to EPiServer (we have version 7) and I'm after some advice about setting up a multi-venue site. By this I mean a single company that owns a set of venues at diffetent locations in the country (or the world). The client would like to have a separate set of pages for each venue, as each venue will have slightly different offerings.

I'd like the set up to work thus...

http://www.myvenue.com/london/en/
http://www.myvenue.com/manchester/en/
http://www.myvenue.com/germany/de

...etc. Each location could potentially have multiple languages too (en, de, jp etc).

What would be the best way to do this in EPiServer? Would I have a single EPiServer site and use page containers for each location, placing the folder structure under each container or would I use a multi-site set up?

They'd like to have an editor property where each venue can upload their own logo to use in the header of their venue's pages. If I was to use the page container method (one page container per venue), how would I set up an editor property that applies to all pages under that container? I.e. an editor property for just the parent container page that affetcs all the child pages.

I hope you can help :-)

Many thanks,
Chris

#75956
Oct 13, 2013 17:34
Vote:
 

A multisite approach would need a license for each site and hence cost you more money.

For the logo property you could use a dynamic property which should be set on each venue container.

#75958
Oct 13, 2013 23:03
Vote:
 

OK, so a page container approach would be better for each venue?

If I were to use a property on the page container, how would I access that property from a page within that container? Sorry if this is an obvious question I'm just not used to how EPiServer works 100% yet :-)

#75966
Oct 14, 2013 11:41
Vote:
 

You need to access that page in some way. 

 

If you have many more properties that are venue specific and should be set at the container level I would create a dynamic pagereference property on the container page and point it to the container page it self.

Then in your usercontrol and templatebase classes you could create a helper property that reads that dynamic property and returns it in the correct type.

Pseudo code:

 

YourContainerPageType HelperProperty

get

{

  // Read value from dynamic property

  // If set get the page and cast it to the correct type and return it.

}

 

Then in your views/templates you can easyli access any settings with ie HelperProperty.LogImage

 

 

#75987
Oct 15, 2013 8:45
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.