Child portals had additional support added in version 03.01.00. We didn't make those updates though. What specific support/features are you looking for with child portals?

Hi Will

I have a number of child portals that I would like to use hotcakes on. The main reason for creating child portals as opposed to having one main store is that each merchant/store needs to have its own payment processor as we don't want to be responsible for paying vendors. Other than that our needs are simplistic in that we don't need multiportal sharing etc. The role capability in terms of managing the store is fine too.

I read your post about child portals, that it's possible to create multiple stores under a dnn instance, and I am testing that now. I am new to the product and finding my way around. Excited to see full potential.

Thanks

Carl

I just want to be sure that we're talking about the same thing...

Site Note: site/portal is the same thing in the examples below.

Typically, "child sites" refers to the scenario where there is one installation of DNN that has many websites on it, but they all have the same domain name. For example, if your domain name is example.com, then the child portals would be example.com, example.com/site1, example.com/site2, example.com/site3, etc.

Another use case is "parent sites," where you again would have one installation of DNN and many websites on it, but the difference would be that they each have a domain name instead of a path, like the previous example. In this use case, the website addresses would be example.com, example2.com, example2.com, store.example.com, etc.

Would you mind confirming which use case you're referring to?

[quote=Will Strohl;970]I just want to be sure that we're talking about the same thing...

Site Note: site/portal is the same thing in the examples below.

Typically, "child sites" refers to the scenario where there is one installation of DNN that has many websites on it, but they all have the same domain name. For example, if your domain name is example.com, then the child portals would be example.com, example.com/site1, example.com/site2, example.com/site3, etc.

Another use case is "parent sites," where you again would have one installation of DNN and many websites on it, but the difference would be that they each have a domain name instead of a path, like the previous example. In this use case, the website addresses would be example.com, example2.com, example2.com, store.example.com, etc.

Would you mind confirming which use case you're referring to?[/quote]

When I first started looking at hotcakes, I thought I would use it on child sites ie: www.website.com/site1...site2 etc but since the admin and store settings are at the host level, it wouldn't work for us. So I created a parent domain ie: site1-store.com and am using it that way. So having the ability to create a full store (admin,products, categories, store settings etc) at the child portal level would be great.

Did I clarify?

thanks