I have a prospective client that wants to have a site design we are working on available to each of their agents (500+ people) as their “own” website to use for the agent's business with their clients. As an example… http://ABC.com/JSmith333 http://ABC.com/BJones444

They want the site master content we create to be what all agents have on their individual child sites. In testing this with a 6.0 instance I can create the export template and use that to create test child sites 1, 2, 3 etc. What I am not able to do yet is have a change I make in the master portal carry over into the child portals. What the client wants is the equivalent to what would happen when copying modules from an existing page into a new page using the "Reference" option. In this case changes to any of these modules on any page is carrried over to all other pages.

Can someone point me in the right direction on how to acheive this in an efficient manner on a website-wide basis (parent -> child 1, 2, 3, n)...?

Thanks -

DotNetNuke does not include content sharing between portals. That functionality is planned for a future release, but I don't know anything else besides that.

There are some third party module that do provide that sort of functionality. You'll find them at Snowcovered.com.

Thanks Joe.

Is it possible to create a "reference" tie back from the child portals to the parent portal with these 3rd party modules such that a change in content on a page on the parent portal is reflected back on all of the child portals...?

I assume that all of these work with only one copy of the content. So, if the content is changed, it will be changed everywhere it is displayed. But, you'll need to check with the developers.

Note that it is a common practice to have demo or trial versions of modules so that you can test them.