What are the footprints a magento module can leave in the magento system?
-
30-09-2020 - |
Question
I installed a module/extension but it does not work well for our needs.
I want to completely delete the module with all its footprints.
I removed the following:
code pool - deleted the folder related to that module under community folder,
deleted design files at design/frontend and design/adminhtml,
deleted email template files of that module at locale//template/email/,
deleted Namespace_ModuleName.xml at etc/modules folder,
removed configuration variable values of that module at core_config_data table,
deleted module entry at core_resource table,
deleted all tables created by that module by looking sql file of the module
what else I need to remove to uninstall the module completely
Am I doing correct or is there any other standard way to uninstall magento extentsion ?
Solution
Here's the personal list I made up over the years:
app/code/<codePool>
folderapp/etc/modules
fileapp/locale
translation and email filesapp/design
layout and template filesjs
librarieslib
librariesskin
js, css and images filesshell
scripts- extra non native folders
Regarding database:
- Tables created by the module
core_config_data
entriescore_resource
entry- Possible extra columns added to native Magento tables
- Possible attributes added to native Magento entities (this is a very important one, especially if a backend model is used, removing the files without removing the attribute could potentially break the websote)
One useful module I use to properly uninstall my personal modules is https://github.com/magento-hackathon/MageTrashApp it lets you create uninstall scripts for both files and database for your modules then you can uninstall them from the backend.