New more user friendly product/variants logic. Let's discuss
- 80
- 894
- 10/12/2012
- United States
a.m. wrote:
same thing happened to me after "successful" build & deploy, however the "Administration\Views\Product\_CreateOrUpdate.SEO.cshtml" is missing in the deployable files. Not sure how or why this occurred for at least two of us, but it's worth noting and possibly looking into.
The partial view '_CreateOrUpdate.SEO' was not found or no view engine supports the searched locations.
Everything works fine out of the box. Do you have the following file? \Nop.Web\Administration\Views\Product\_CreateOrUpdate.SEO.cshtml
Everything works fine out of the box. Do you have the following file? \Nop.Web\Administration\Views\Product\_CreateOrUpdate.SEO.cshtml
same thing happened to me after "successful" build & deploy, however the "Administration\Views\Product\_CreateOrUpdate.SEO.cshtml" is missing in the deployable files. Not sure how or why this occurred for at least two of us, but it's worth noting and possibly looking into.
- 132
- 1848
- 1/3/2010
- Spain
Suggestions.
- Associated product should have the option of defining display order, like related product tab.
{
- An associated product should not be accesible from url or search box (like now works Product-Product variants). If you search camera, you will get the 3 items an only should appear one.
OR
-If associated product is accesible from search box, the product should display price, etc . Now, nopcommerce works this way if we set the "Product" as Grouped Product and the "Product Variant" as Simple Product (using their respective templates), so, you can purchase this product from the list of the grouped product or as a simple product.
OR
- Let admin to decide if these products will be accesible from searchbox using a check box (maybe, there are some products that will not need to allocate in a category and the store owner only wants to sell it as "product variant").
}
- Associated product should have the option of defining display order, like related product tab.
{
- An associated product should not be accesible from url or search box (like now works Product-Product variants). If you search camera, you will get the 3 items an only should appear one.
OR
-If associated product is accesible from search box, the product should display price, etc . Now, nopcommerce works this way if we set the "Product" as Grouped Product and the "Product Variant" as Simple Product (using their respective templates), so, you can purchase this product from the list of the grouped product or as a simple product.
OR
- Let admin to decide if these products will be accesible from searchbox using a check box (maybe, there are some products that will not need to allocate in a category and the store owner only wants to sell it as "product variant").
}
Team Member
- 16619
- 155940
- 10/22/2008
- Armenia
sabueXo wrote:
Thanks for suggestion
sabueXo wrote:
Already thought about it. This sub-work-item is already on the roadmap. I'm going to implement it the following way. A store owner will be able to choose one on the following visibility modes: "Catalog and Search" or "Catalog" . This way you can hide some product from searching (by some keyword)
Associated product should have the option of defining display order, like related product tab.
Thanks for suggestion
sabueXo wrote:
...If you search camera, you will get the 3 items an only should appear one...
Already thought about it. This sub-work-item is already on the roadmap. I'm going to implement it the following way. A store owner will be able to choose one on the following visibility modes: "Catalog and Search" or "Catalog" . This way you can hide some product from searching (by some keyword)
Team Member
- 16619
- 155940
- 10/22/2008
- Armenia
sabueXo wrote:
Search engines will see the same information what any other customers see. If a customer cannot visit some product details page, then the same can be told about the search engines.
Google should find only pages that are marked as "Catalog and Search" and return 404 for other ones to avoid the indexing of these pages?
Search engines will see the same information what any other customers see. If a customer cannot visit some product details page, then the same can be told about the search engines.
- 80
- 894
- 10/12/2012
- United States
tier prices calculated on multiple attribute choices...
currently, tier prices can only be obtained when a customer selects the tier threshold of a single attribute, such as 5 items of one size of a product. will the new product logic account for tier calculations based on multiple attribute selections meeting the tier threshold - such as 2 small + 3 large of the same product gives you the 5 items price? I can't introduce tier pricing until this is implemented.
currently, tier prices can only be obtained when a customer selects the tier threshold of a single attribute, such as 5 items of one size of a product. will the new product logic account for tier calculations based on multiple attribute selections meeting the tier threshold - such as 2 small + 3 large of the same product gives you the 5 items price? I can't introduce tier pricing until this is implemented.
Team Member
- 16619
- 155940
- 10/22/2008
- Armenia
mattbrummett wrote:
Sorry, haven't got your question. Tier prices will work absolutely the same way as they worked before. It's logic wasn't changed when refactoring old product variant logic. Could you please provide some example?
tier prices calculated on multiple attribute choices...
currently, tier prices can only be obtained when a customer selects the tier threshold of a single attribute, such as 5 items of one size of a product. will the new product logic account for tier calculations based on multiple attribute selections meeting the tier threshold - such as 2 small + 3 large of the same product gives you the 5 items price? I can't introduce tier pricing until this is implemented.
currently, tier prices can only be obtained when a customer selects the tier threshold of a single attribute, such as 5 items of one size of a product. will the new product logic account for tier calculations based on multiple attribute selections meeting the tier threshold - such as 2 small + 3 large of the same product gives you the 5 items price? I can't introduce tier pricing until this is implemented.
Sorry, haven't got your question. Tier prices will work absolutely the same way as they worked before. It's logic wasn't changed when refactoring old product variant logic. Could you please provide some example?