My products require users to enter a few fields of info in text, boolean, and number. Is there a way to this in this system. I thought that may be attributes would be a good match.
Also, if I need to make programming changes, could you give me a hint on the best way to handle it. If there is something in the system that facilitates this kind of thing. This way I won't 1) reinvent the wheel 2) ruin structural integrity.
Thanks in advance
Product Attributes
MVP
- 751
- 4113
- 1/24/2009
- United Kingdom
If you require the user to make a text entry then within administration, go to the product variant and tick the "Requires Text Option" checkbox and then enter a prompt (you can only add one of these).
If you know the available options in advance e.g. True/False or Colour (Red, Green, Blue) etc., then attributes are most suitable.
As for programming changes, you will need Visual Studio. Whilst nopCommerce is very easy to extend, there is no predefined API that allows you to plug new bits in. There are the following considerations:
1) If you are developing something new, check to see if it's already on development roadmap - it may save you a lot of work.
2) nopCommerce follows the n-tier design principle and is provider based. If you following the same principles in your own developments with nc it will improve overall interoperability
3) make sure that any developments are independent from the base application. An example of this would be if you wanted to create some custom logic on a nopCommerce page. It would be better to package this in a user control or separate assembly as any changes you make yourself will obviously not in the next release of nopCommerce. Basically you want to make sure you can apply new releases whilst making it easy to reapply any custom developments you have made.
4) Finally, consider whether any developments you make would be useful to the community. This will not only mean you can help others, it will also save you having to reapply your changes on every release, as they can become "part of" the release.
Hope this helps you,
Thanks,
Ben
If you know the available options in advance e.g. True/False or Colour (Red, Green, Blue) etc., then attributes are most suitable.
As for programming changes, you will need Visual Studio. Whilst nopCommerce is very easy to extend, there is no predefined API that allows you to plug new bits in. There are the following considerations:
1) If you are developing something new, check to see if it's already on development roadmap - it may save you a lot of work.
2) nopCommerce follows the n-tier design principle and is provider based. If you following the same principles in your own developments with nc it will improve overall interoperability
3) make sure that any developments are independent from the base application. An example of this would be if you wanted to create some custom logic on a nopCommerce page. It would be better to package this in a user control or separate assembly as any changes you make yourself will obviously not in the next release of nopCommerce. Basically you want to make sure you can apply new releases whilst making it easy to reapply any custom developments you have made.
4) Finally, consider whether any developments you make would be useful to the community. This will not only mean you can help others, it will also save you having to reapply your changes on every release, as they can become "part of" the release.
Hope this helps you,
Thanks,
Ben