Remove standard OC modules?

Dear forum friends,

I have a wish to completely remove (not just deactivate) as much as possible of all build in modules that come like standard in a OC installation. Of course modules that I'm not using. My current version is 3.0.3.2.

How is this done in best possible way? Is FTP the only way in the end???

Yes, FTP is the only way. You need to remove controller, if you simply don't want them to be displayed in the list. But if you want to remove all files, then you need to remove catalog, mode, language and view both in admin and catalog folders. Sometimes library as well.

model . From database as well.

Jassim1 wrote: ↑

Sat Jun 19, 2021 11:46 am

Dear forum friends,

I have a wish to completely remove (not just deactivate) as much as possible of all build in modules that come like standard in a OC installation. Of course modules that I'm not using. My current version is 3.0.3.2.

How is this done in best possible way? Is FTP the only way in the end???

Was it you who asked this before and everyone told you not to do it?

Anyway if it wasn't; don't do it, there is no good reason to.

Jassim1 wrote: ↑

Sat Jun 19, 2021 11:46 am

Dear forum friends,

I have a wish to completely remove (not just deactivate) as much as possible of all build in modules that come like standard in a OC installation. Of course modules that I'm not using. My current version is 3.0.3.2.

How is this done in best possible way? Is FTP the only way in the end???

This code should be placed in the install() method of your controller. This will then be run when your mod is installed under EXTENSIONS > MODULES in the administrator area. Just add this to your controller and it should work (untested)

paulfeakins wrote: ↑

Mon Jun 21, 2021 7:52 pm

Jassim1 wrote: ↑

Sat Jun 19, 2021 11:46 am

Dear forum friends,

I have a wish to completely remove (not just deactivate) as much as possible of all build in modules that come like standard in a OC installation. Of course modules that I'm not using. My current version is 3.0.3.2.

How is this done in best possible way? Is FTP the only way in the end???

Was it you who asked this before and everyone told you not to do it?

Anyway if it wasn't; don't do it, there is no good reason to.

I have read several times that the preinstalled modules should not be removed, I am very curious to know if there is a good reason not to, I think reducing the clutter of a heap of modules that I am never going to use is a very good reason to remove them. Is it likely to cause problems if they are removed?

AliceH wrote: ↑

Mon Jan 20, 2025 3:12 pm

I have read several times that the preinstalled modules should not be removed, I am very curious to know if there is a good reason not to, I think reducing the clutter of a heap of modules that I am never going to use is a very good reason to remove them. Is it likely to cause problems if they are removed?

It would be better to hide them in that case.

The only way you could remove some of the standard modules is by disabling them first in the admin backend, and then to manually remove the files, e.g.

admin/controller/extension/module/xxx.php
admin/language/*/extension/module/xxx.php
admin/model/extension/module/xxx.php
admin/view/extension/module/xxx.twig

catalog/controller/extension/module/xxx.php
catalog/language/*/extension/module/xxx.php
catalog/model/extension/module/xxx.php
catalog/view/theme/*/template/extension/module/xxx.twig

Though IMHO it's not worth the trouble.