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 ...Multi URL/Alias on single portal, parent portals, o child portals?  ::  SquareBallsFootballLeagueMulti URL/Alias on single portal, parent portals, o child portals? :: SquareBallsFootballLeague
Previous
 
Next
New Post
2/10/2016 4:54 AM
 

- -writing this post seeking for advice, before further development - -

We are developing our portal with self-develop modules to cover extra functionality within dnn. And planning to extend to use the same portal under several domains. Lets take as example that our portal will be SquareBallsFootballLeague.com, in which we track these famous sport, we give statistics for the teams, for their players, we allow player to register and apply for a team, or keep score tracking and vote for their favourite team, etc...

That wise, under SquareBallsFootballLeague.com, we have pages as 

  • SquareBallsFootballLeague.com/teams, all teams of the league
  • SquareBallsFootballLeague.com/teams/SquareMagicBulls, team page
  • SquareBallsFootballLeague.com/Statistics, all league statistics

Well, now comes the multiportal part. We want to create specific team pages under their own domain, like SquareMagicBulls.com

These team portals should allow:

  • Generate the portal with similar, but not exact the same data and format than SquareBallsFootballLeague.com/teams/SquareMagicBulls
    (we will be developing own module for that) but will need to be able to apply different skin to the team portal
  • MUST: Share users, and users logins with SquareBallsFootballLeague.com, preferable single-sign-on should be posible

  • Allow pages to be share between "league portal" and "team portal" (that can be done at module level)
    SquareBallsFootballLeague.com/Statistics and SquareMagicBulls.com/Statistics should be same page, even we pre-filter in our module to the specifics of the team.  (and so the 404, 500, sign_in)

So, in this scenario, how should we develop our "chain of portals" ?

As different Alias on same portal, as separate parent Portals, or as Child portals, or maybe another solution you can suggest ?

 

 
New Post
2/10/2016 5:42 AM
 
this would be possible using site groups. If using free DNN platform, you'll need to download and install Sitegroup Manager module from http://dnnportalgroups.codeplex.com/

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/11/2016 8:23 AM
 
Sebastian Leupold wrote:
this would be possible using site groups. If using free DNN platform, you'll need to download and install Sitegroup Manager module from http://dnnportalgroups.codeplex.com/

thanks for the response !

using SiteGroupManager will solve the login issues, perfect,

on top of that, for a setup like ours, what would be more convenient ? all parent portals, o parents and child ones ??

 
New Post
2/12/2016 2:13 PM
 
parent or child portal is just a question of domain names - and sometimes cookies.
I'd prefer dedicated domain / server names (marketing.mydomain.com, production.mydomain.com...)

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Multi URL/Alias on single portal, parent portals, o child portals?  ::  SquareBallsFootballLeagueMulti URL/Alias on single portal, parent portals, o child portals? :: SquareBallsFootballLeague


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.

Content Layout

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out