Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...How to Setup Site / Portals for White Labelling?How to Setup Site / Portals for White Labelling?
Previous
 
Next
New Post
8/29/2011 10:55 AM
 
Hi,

I'm trying to accomplish the following:
I have a client and my client wants to use functionality on my website for their clients but it should look as if this functionality / module is located on their website. How can I do this?

More specifically:
If their client types www.MyProduct.MyClientsSite.com (or www.MyClientsSite.com/MyProduct) their client is redirected to a page (or may be portal) on my website. What should I do in DotNetNuke to make this possible? What are the limits?

The following is probably necessary:
* My client should add an entry (for www.MyProduct.MyClientsSite.com) in their DNS referring to the IP address of my site.
* I should have a page (or may be even a portal?) which looks as if it is the site of my client.
* I should add a portal alias to my site (www.MyProduct.MyClientsSite.com) and have "PortalAlias Mapping Mode" set to "None". (Isn't it possible to do this with "PortalAlias Mapping Mode" set to "Redirect"?)

Is this correct? Am I overlooking things?

Thx.
 
New Post
8/30/2011 12:12 PM
 
'Custom branding' might be a better term to use instead of 'white labelling' to describe what I'm trying to accomplish.
 
New Post
8/30/2011 12:36 PM
 
DNN supports both parent and child portals  on the same hosting.

The advantage of CHILD hostings for your scenario is that you dont need to mess around with dns and aliasing - instead you use paths
www.mysite.com/myproduct/  - www,mysite.com/myproduct2/

Each functions as an individual portal - it can have its own skin and its own administration access.

Westa
 
New Post
8/30/2011 12:48 PM
 
Thank you Wes(ta).

I was hoping that clients would not be able to see (from the URL) that they are on my site. Would that be possible?
 
New Post
8/30/2011 1:21 PM
 
If you go down the Parent Portal route then you can setup each with their own entirely separate domains.

But you will need to handle the DNS records - and the IIS alias settings.

NOTE HOWEVER - that these are entirely separate portals - no content is shared between the portals as such - so you will need to add individual content to each portal.

Alternatively, if all you want is the SAME content for each site - but just a different LOOK to the content - then you could look at a skin switcher - based on the domain name.

In this case - all the aliases would be setup to point to the same portal  - and the skin stylesheet could be changed to present a different LOOK for each client

http://www.40fingers.net/WeblogsNews/...

has a great tool that does this sort of thing.

Westa
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...How to Setup Site / Portals for White Labelling?How to Setup Site / Portals for White Labelling?


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out