Hey everyone!
I'm looking at adding a new type of product, quite similar to a Gift Card but is handled differently during checkout.
In an old version of NOP that is heavily customized, I altered the core source to implement this. We are now upgrading to 3.7 so i'd like to use plugins, if possible.
Question is:
Is it possible to create a plugin to add a new product type (such as adding a checkbox to the Admin product details page) and showing it in the front-end store without changing the Core source? If so, can anyone point me to an example plugin? I'm trying learn how to develop plugins but haven't seen anything like this yet.
Thanks!
Ryan
New Type of Product - Plugin?
MVP
Sviluppatori certificati
- 1623
- 15968
- 25/11/2013
- Bangladesh
rymos wrote:
You can do it. But I think if you use it for your own or one project changing core code is better. And already you know where need to change. Any new feature can easily added by customizing core code. On the other hand Plugin is better for generalizing. Note: I expect Nop Team explanation about it. Am I right or wrong?
Hey everyone!
I'm looking at adding a new type of product, quite similar to a Gift Card but is handled differently during checkout.
In an old version of NOP that is heavily customized, I altered the core source to implement this. We are now upgrading to 3.7 so i'd like to use plugins, if possible.
Question is:
Is it possible to create a plugin to add a new product type (such as adding a checkbox to the Admin product details page) and showing it in the front-end store without changing the Core source? If so, can anyone point me to an example plugin? I'm trying learn how to develop plugins but haven't seen anything like this yet.
Thanks!
Ryan
I'm looking at adding a new type of product, quite similar to a Gift Card but is handled differently during checkout.
In an old version of NOP that is heavily customized, I altered the core source to implement this. We are now upgrading to 3.7 so i'd like to use plugins, if possible.
Question is:
Is it possible to create a plugin to add a new product type (such as adding a checkbox to the Admin product details page) and showing it in the front-end store without changing the Core source? If so, can anyone point me to an example plugin? I'm trying learn how to develop plugins but haven't seen anything like this yet.
Thanks!
Ryan
You can do it. But I think if you use it for your own or one project changing core code is better. And already you know where need to change. Any new feature can easily added by customizing core code. On the other hand Plugin is better for generalizing. Note: I expect Nop Team explanation about it. Am I right or wrong?
- 10
- 50
- 30/04/2014
- United States
anik1991 wrote:
Great! I'm not sure where to start. Can you point me to an example plugin or something to get me started?
Yes you can do that. For that you have override admin product route and implement your own design.
Thanks very much. Would I also override the checkout process in the plugin as well?
yes you can override checkout process from plugin.
Thanks very much. Would I also override the checkout process in the plugin as well?
yes you can override checkout process from plugin.
Great! I'm not sure where to start. Can you point me to an example plugin or something to get me started?
- 425
- 3039
- 21/03/2012
- Brazil
sohelcse10_duet wrote:
You can do it. But I think if you use it for your own or one project changing core code is better. And already you know where need to change. Any new feature can easily added by customizing core code. On the other hand Plugin is better for generalizing. Note: I expect Nop Team explanation about it. Am I right or wrong?
Keep in mind that nopCommerce 4.0 will change a lot (3.8 will be the last one using MVC 5), so, make it easier and more flexible as you can, will help you upgrading later.
You can do it. But I think if you use it for your own or one project changing core code is better. And already you know where need to change. Any new feature can easily added by customizing core code. On the other hand Plugin is better for generalizing. Note: I expect Nop Team explanation about it. Am I right or wrong?
Keep in mind that nopCommerce 4.0 will change a lot (3.8 will be the last one using MVC 5), so, make it easier and more flexible as you can, will help you upgrading later.
MVP
Sviluppatori certificati
- 615
- 6363
- 03/03/2015
- Bangladesh
ivanslater wrote:
You can do it. But I think if you use it for your own or one project changing core code is better. And already you know where need to change. Any new feature can easily added by customizing core code. On the other hand Plugin is better for generalizing. Note: I expect Nop Team explanation about it. Am I right or wrong?
Keep in mind that nopCommerce 4.0 will change a lot (3.8 will be the last one using MVC 5), so, make it easier and more flexible as you can, will help you upgrading later.
Yes but it will release at least 1.5 year and needs to do lots of changes. By doing it in core code or plugin. we have to change a lot then.
You can do it. But I think if you use it for your own or one project changing core code is better. And already you know where need to change. Any new feature can easily added by customizing core code. On the other hand Plugin is better for generalizing. Note: I expect Nop Team explanation about it. Am I right or wrong?
Keep in mind that nopCommerce 4.0 will change a lot (3.8 will be the last one using MVC 5), so, make it easier and more flexible as you can, will help you upgrading later.
Yes but it will release at least 1.5 year and needs to do lots of changes. By doing it in core code or plugin. we have to change a lot then.