Multi-store roadmap. Let's discuss (UPDATE: done)

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
11 years ago
sch09 wrote:
i have also noticed that featured products under categories not enabled for a given store , still show on the home page.

If you hide a category from a store, it only hides the name of the category not the products in that category. I think that a category by itself is nothing but a logical container for products so if someone hides a category there should be a check box which should iterate through the products and hide the products within that category. Just hiding the category name has no use as you can search all the products in that category  and also shows them everywhere on the website like homepage etc.
11 years ago
sch09 wrote:
one question: can different stores be under subdomains ? that would be a very convenient feature for many merchants.

Yes. Supported
11 years ago
Different shipping options per store is essential in my case.  Or different plugin assignments for shipping for store.
11 years ago
is it possible to assign dedicated app pool to each store?
the reason is that if store1 crashed or down, it won't affect store2 and store3....

are there any new discount rules been introduced along with the multi-store feature, example:
- customers can have discount $10 in store1 if they have already purchased $100 in store2
- discount code ABC can be used in store1 and store2 but not store3
- if customer is VIP in store1, he can enjoy $5 off in store2 and $10 off in store3
something like these....
11 years ago
Andrei!! I downloaded the latest changeset (d3e7dd02cde0) and noticed that in IIS 7.5 does not work with the "Managed Pipeline Mode" in "Integrated". Only in "classic". It is shown the error "Request is not available in this context". Maybe it has something to do with the changeset d5c4566baad0 .

More details of the error:

Line 128:            string result = string.Empty;
Line 129:
Line 130:            if (_httpContext == null || _httpContext.Request == null)
Line 131:                return result;
Line 132:

Source File: c:\Users\Nei\web\Nop-teste\Libraries\Nop.Core\WebHelper.cs    Line: 130

Stack Trace:


[HttpException (0x80004005): Request is not available in this context]
   System.Web.HttpContext.get_Request() +9718452
   System.Web.HttpContextWrapper.get_Request() +28
   Nop.Core.WebHelper.ServerVariables(String name) in c:\Users\Nei\web\Nop-teste\Libraries\Nop.Core\WebHelper.cs:130
   Nop.Web.Framework.WebStoreContext.get_CurrentStore() in c:\Users\Nei\web\Nop-teste\Presentation\Nop.Web.Framework\WebStoreContext.cs:37
   Nop.Web.Framework.SettingsSource.<BuildRegistration>b__5(IComponentContext c, IEnumerable`1 p) in c:\Users\Nei\web\Nop-teste\Presentation\Nop.Web.Framework\DependencyRegistrar.cs:338
..............
11 years ago
infiniti wrote:

If you hide a category from a store, it only hides the name of the category not the products in that category. I think that a category by itself is nothing but a logical container for products so if someone hides a category there should be a check box which should iterate through the products and hide the products within that category. Just hiding the category name has no use as you can search all the products in that category  and also shows them everywhere on the website like homepage etc.


Products can be in more than one category. Un-publishing a category should not effect the products it contains.
11 years ago
thrifty34 wrote:
Different shipping options per store is essential in my case.  Or different plugin assignments for shipping for store.

I've not yet had time to look at the new version, but I suspect that different shipping rate computation methods (plugins) is exactly what you would get - plugins are loaded from the app's \Plugins folder and their "status" (installed?) is stored in the app's InstalledPlugins.txt file.   That said, however, since multiple sites are sharing the same database, the shipping "options" and rates for the stores using the same plugin(s) will be the same for each site.   I hope to be able to address this with Shipping Director.
11 years ago
nopDev wrote:
is it possible to assign dedicated app pool to each store?
the reason is that if store1 crashed or down, it won't affect store2 and store3....

are there any new discount rules been introduced along with the multi-store feature, example:
- customers can have discount $10 in store1 if they have already purchased $100 in store2
- discount code ABC can be used in store1 and store2 but not store3
- if customer is VIP in store1, he can enjoy $5 off in store2 and $10 off in store3
something like these....


I wouldn't think there would be more than one AppPool.  There's only one website in IIS, right?
11 years ago
AndyMcKenna wrote:

I wouldn't think there would be more than one AppPool.  There's only one website in IIS, right?


yes you are right. however i believe split to different app pool will get the whole system more robust.
11 years ago
AndyMcKenna wrote:
is it possible to assign dedicated app pool to each store?
the reason is that if store1 crashed or down, it won't affect store2 and store3....

are there any new discount rules been introduced along with the multi-store feature, example:
- customers can have discount $10 in store1 if they have already purchased $100 in store2
- discount code ABC can be used in store1 and store2 but not store3
- if customer is VIP in store1, he can enjoy $5 off in store2 and $10 off in store3
something like these....

I wouldn't think there would be more than one AppPool.  There's only one website in IIS, right?


** It's important to note that this is a multi-store solution.  One owner, with several websites (like our company has several nopCommerce sites.  So, this isn't talking about "one" website with several owners.

In IIS, you make as many websites as you want, and they usually are assigned to a "default" app pool.

However, you can make as many application pools as you like.

- you just have to assign each different site to a specific application pool, or it will get the "default".
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.