nopCommerce 3.30 roadmap and estimated release date. Let's discuss.

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
10 years ago
Looks great! Noticed a few things mentioned below...

1) Adding a text box does let us set max & min character allowances, but doesn't let us apply a charge if text is entered. Not sure what the purpose of validation rules is unless we can decide if that includes a charge or not.

2) When we add a validation for rule for a textbox control, we can no longer generate attribute combinations. Can we simply take any textbox controls out of the equation when calculating attribute combinations because they're custom options aside from inventory anyway.

3) Just as we have for "Specification Attributes" where we can add options and save them as templates, can this functionality be carried over to Product Attributes as well? It would save those of us with ever-changing color pallets and style availability (textile, apparel, etc) from having to change hundreds, if not thousands of products, when we could have just made one simple "color name" change or removed a particular option if it's not available anymore.

Thanks for your consideration on these points and thank you for your hard work! :)
10 years ago
mattbrummett wrote:
Looks great! Noticed a few things mentioned below...

1) Adding a text box does let us set max & min character allowances, but doesn't let us apply a charge if text is entered. Not sure what the purpose of validation rules is unless we can decide if that includes a charge or not.

2) When we add a validation for rule for a textbox control, we can no longer generate attribute combinations. Can we simply take any textbox controls out of the equation when calculating attribute combinations because they're custom options aside from inventory anyway.

3) Just as we have for "Specification Attributes" where we can add options and save them as templates, can this functionality be carried over to Product Attributes as well? It would save those of us with ever-changing color pallets and style availability (textile, apparel, etc) from having to change hundreds, if not thousands of products, when we could have just made one simple "color name" change or removed a particular option if it's not available anymore.

Thanks for your consideration on these points and thank you for your hard work! :)

Hi Matt,

Thanks. Please find answers below:

1. Charges for textbox attributes (attributes without values) are not supported. It's not somehow related to validation rules. Anyway, please vote for this work item here

2. Actually you should not use attribute combinations with textboxes/file upload/datepicker attributes. It's just useless because you cannot specify all possible combination (a customer can enter any value). It's also stated on the combinations tab on the product details page - "Also note that some attribute control types that support custom user input (e.g. file upload, textboxes, date picker) are useless with attribute combinations"

3. You can find a similar work item here. But not sure that it'll ever be implemented because you can simply create a sample unpublished product with required attributes, and then just use "copy product" functionality (when you need to create a new product).
10 years ago
Hi,

Updated from 3.1 to 078ec7b7b121

Error:
Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.

Source Error:


Line 117:            {
Line 118:                foreach (var a in assemblies)
Line 119:                {
Line 120:                    Type[] types = null;
Line 121:                    try
10 years ago
mattbrummett wrote:

2) When we add a validation for rule for a textbox control, we can no longer generate attribute combinations. Can we simply take any textbox controls out of the equation when calculating attribute combinations because they're custom options aside from inventory anyway.

https://www.nopcommerce.com/boards/t/27525/suggestion-combinablenon-combinable-product-attributes.aspx
10 years ago
we cant use nopCommerce for fashion sites , is there any plan to add multisellect ajax or any other product spesification filter in nop futures ?  this is the mainly future for all %80 fashion web sites , prestashop 1.6 has great example  http://demo-store.prestashop.com/en/8-dresses
10 years ago
webxpro wrote:
we cant use nopCommerce for fashion sites , is there any plan to add multisellect ajax or any other product spesification filter in nop futures ?  this is the mainly future for all %80 fashion web sites , prestashop 1.6 has great example  http://demo-store.prestashop.com/en/8-dresses

There are plenty of plugins that do what you are asking for. Go to Downloads-> Extensions and Themes.
10 years ago
i dont see any opensource plugin there about which i ask and all multi sellect plugins  and themes are with payment i ask about the futures of nopCommerce new versions modules.
10 years ago
webxpro wrote:
i dont see any opensource plugin there about which i ask and all multi sellect plugins  and themes are with payment i ask about the futures of nopCommerce new versions modules.

Please vote for this work item here
10 years ago
thank you andrei i already added  https://nopcommerce.codeplex.com/workitem/12017

in nopCommerce when we add products we have color attributes and spesifications for the products and we even choice colors from the color palette but in filter we dont see any color to make filter products and i can say  that nopCommerce will be more populer only because of this futures too for the fashion site owners.  sure all the big companys has programmers to make this plugin and use but for the own company owners who need just site this is not easy and ready plugins with payments are not open source and it is not easy to host compiled dll if we dont know what it do.
10 years ago
vladundhanna wrote:
Hi,

Updated from 3.1 to 078ec7b7b121

Error:
Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information...

Can we upgrade directly from 3.1 or should we go 3.1->3.2->3.3 without any risks?
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.