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

Yes, you did. The only thing you'll need to do in this case is to manually add the Hotcakes Administration page to the Admin menu, or provide that link in another way.

Thanks Will! Still learning what hotcakes can do. So far so good!

Carl

Hi Will

I successfully installed hotcakes on a parent portal (still under one dnn install). I then created another parent portal under the same dnn install

Websiteparent.com

- website1.com (ran wizard and all worked pages created etc)
- website2.com - Ran wizard and it hung on step one. Did not create pages. I was able to go into admin and set up everything manually, ie: set store name, create pages etc and I am able to add categories and products etc.

The only thing that does not work are images. The url is rendered with an additional slash and the image is not found.

Category Image - http:///DesktopModules/Hotcakes/Core/Admin/Images/MissingImage.png

Product image - http:///Portals/63/Hotcakes/Data/products/2094e4ee-0b3c-4bea-8171-3b11b26f305f/small/BraceletBlue.png

Portal 63 for the product image is correct. But the catagory image isn't referencing a portalid. Does this mean even though the store is installed on a unique domain, the categories are global for all portals?

or could there be something else going on?

Do you think you may be running into this issue?

https://github.com/Hotcak...erce-core/issues/153

Hi Will

I don't think so. the images are uploaded using hotcakes and not imported. For some reason the urls for the images are written with 2 extra slashes. Any idea where I could check ie webconfig, database etc. to see what would cause this. it's almost as if it doesn't know what domain the install works with.

http:[b]//[/b]/Portals/63/Hotcakes/Data/categoryicons/ff857a61-e202-49ba-8fbd-463ce325e40f/small/americanwhosensation2.png

The portal alias is correct. The top level parent works ok.

Hi Will

I resolved the image problem. I restored my site back to pre-hotcakes. Instead of installing (running the wizard) hotcakes on the top level parent and then using the wizard to install it on the new parent portal, I installed it directly from the new domain. All works ok. Although I don't know what will happen when I run the wizard on another parent.

Look forward to using hotcakes.

Carl

Please know that an issue has been created in GitHub to resolve this. Please feel free to include any additional screenshots and/or other errors and details you might have there.

https://github.com/Hotcak...erce-core/issues/161