Adding/Removing functionality

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
4 years ago
Is there a recommended flow for removing functionalities from nopCommerce to suit specific Project needs in a sane way? Say the Blog support
4 years ago
1) If you are looking to hide a few pages then you can make use of access control list
2) If you are looking to add/remove some add-ons like some of the payment plugins, shipping providers, external authentications then you can do so by adding/removing the plugins.
3) If you are looking to customize the implemented functionality(blog) then you can do so by extending/overriding the default features by plugins or by customizing the source code directly.
4) IF you want to add entirely new features then you can achieve this by building/integrating plugins or by customizing the source code. You can either build a new plugin or get the required plugins from the marketplace if it's available.

You can add/remove functionality in multiple ways depending upon your needs. If you are looking (or have a plan) to upgrade your web-shop to the newer version of NopCommerce in the future then customizing with the plugin will be fruitful.
4 years ago
I most need to understand the complete removal of the functionality. However almost everything is interconnected in the app so there are way too many references of the same thing. I was attempting to simply remove parts of code but that seems to lead to the breaking of sth else and a pointless process due to the time it takes.
4 years ago
Hello,

sanju.dahal741 laid out for the best way to modify nopCommerce (including removing functionalities). As he pointed out, it is best to overwrite or extend the code of nopCommerce and not to remove or change it. The best way to do that is to use plugins regardless of whether you write them yourself or you use a plugin by one of the developers in this community.
Removing of functionality will be best executed if you overwrite the source of that functionality - controller, component, factory or a service. Everything else depends on the functionality you want to remove.
If you want more detailed help you will need to give us more details on the functionality you want to remove so we can give you tips.

Hope that helps!

Regards,
Anton
4 years ago
Also, there are many "Settings" that will disable functionality (E.g. Estimated Shipping, Blogs, Forums, etc., etc.)
4 years ago
Thank you all for the answers. Am aware of the capability of admin settings so this referred to what that doesn't cover.  I'll be looking into plugin development for nopcommerce and get back to this thread/create a new one if needed .
One strategy-oriented question if you could honestly answer: For a team of junior devs who have to build a rather basic E-Commerce ASP.NET MVC app, is it better to take advantage of this rather huge framework that is nopCommerce or start from scratch?
Thank you in advance!
4 years ago
Hello,

Definitely, use the framework. It is rather hard to get the required knowledge to work properly with the nopCommerce since it has a huge codebase but the time invested in learning that code will pay off many times in the future.
Many of the code you will need to write for your project is already written into the framework and it can be used pretty easily. Furthermore, newer versions of nopCommerce are highly extendable and it is easy to add, remove or overwrite functionalities without that much knowledge (perfect for junior devs).
Also, relying on the framework and using its code will make you and your developers less responsible for the code you wrote. What I mean is you will be using code that you know will always work since there is a whole dev team (nopCommerce dev team) that is taking care of it.

Hope that helps!

Regards,
Anton
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.